Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Tasks
After completing each task in subagent-driven development, request a code review by dispatching a general-purpose subagent with the code-reviewer.md template
Before merging to main, request a code review with the base and head git SHAs to verify the work meets requirements
When stuck on a problem, dispatch a code reviewer subagent to gain a fresh perspective on the work product
Inputs
Brief summary of what you built (DESCRIPTION)
Plan or requirements describing what the work should do (PLAN_OR_REQUIREMENTS)
Starting commit SHA (BASE_SHA)
Ending commit SHA (HEAD_SHA)
Outputs
Code review feedback from the subagent including strengths, issues categorized as Critical/Important/Minor, and a readiness assessment
Limitations and checks
The reviewer receives precisely crafted context only, never your session's history or thought process
Proceeding with unfixed Important issues is flagged as a red flag and should not be done
Verify BASE_SHA and HEAD_SHA values are correctly set using git rev-parse before dispatching the reviewer
Confirm the code-reviewer.md template has all placeholders filled: DESCRIPTION, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA
Ensure all Critical issues returned by the reviewer are fixed immediately before proceeding
Ensure all Important issues are fixed before moving on to the next task
Verify the dispatched subagent context contains the work product details, not your session history
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control