code-quality

Check configured LSP servers and their status

Comprehensive project review with TODO validation and claim verification

Sync project memory and update hack/ files before ending session

Start a session by loading project context or initializing new project

Use when designing system architecture, evaluating technology choices, planning large-scale refactoring, or answering "how should I structure", "what's the best architecture for", "design the system" questions

Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

Use when investigating performance issues, optimizing slow code, analyzing bottlenecks, or when user mentions "slow", "performance", "latency", "memory", "CPU", "optimization", "bottleneck"

Verifies implementation against plan file tasks. Reads plan, extracts tasks/checkboxes, verifies each against git diff and source code, escalates unchecked tasks via AskUserQuestion.

Use when user needs multi-stakeholder analysis, business impact assessment, or wants perspectives from different roles. Triggers on: "analyze from business perspective", "what would stakeholders think", "impact analysis", "business case for", "ROI of"

Interactive bug investigation workflow using background agents. Use when the user says "I'm going to report bugs", "let's hunt bugs", "investigate these issues", or describes wanting to report issues one-by-one while agents investigate in parallel. Also activates when the user reports a bug/issue and a BUGS.md file exists or was recently created.

Multi-agent PR review with finding verification. Use when asked to "review PR", "review this PR", "code review", or given a PR URL to review. Spawns 6 parallel specialized reviewers (security, QA, performance, code quality, correctness, plan adherence), verifies findings by investigating source code, categorizes by type, and prints a structured report to the terminal. Never comments on GitHub PRs.

Use when about to claim ANY work is complete — code, research, planning, config, or general answers. Also after /swarm, /spawn, subagent-driven development, or any significant deliverable.

Use when user requests deep research, comprehensive analysis, or thorough investigation. Triggers on: "research X thoroughly", "deep dive into", "comprehensive analysis of", "investigate X exhaustively", "compare X options", "evaluate alternatives for". Supports two modes: External (web research, current behavior) and Bridged (internal project investigation followed by external best-practices research).