Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Requesting Code Review Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. Core principle: Review early, review often. When to Request Review Mandatory: After each task in subagent driven development After completing major feature Before merge to main Optional but valuable: When stuck (fresh perspective) Before refactoring (baseline check) After fixing complex bug How to Request 1. Get git SHAs: 2. Dispatch code reviewer subagent: Dispatch a general purpose subagent, filling the template at [code reviewer.md](code reviewer.md) Placeholders: {DESCRIPTION} Brief summary of what you built {PLAN OR REQUIREMENTS} What it should do {BASE SHA} Starting commit {HEAD SHA} Ending commit 3. Act on feedback: Fix Critical issues immediately Fix Important issues before proceeding Note Minor issues for later Push back if reviewer is wrong (with reasoning) Example Common Rationalizations Excuse Reality "I'll just review the diff myself instead of dispatching a reviewer" You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. "The reviewer needs my whole session history to understand the change" Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. Red Flags Never: Skip review because "it's simple" Ignore Critical issues Proceed with unfixed Important issues Argue with valid technical feedback If reviewer wrong: Push back with technical reasoning Show code/tests that prove it works Request clarification See template at: [code reviewer.md](code reviewer.md)

requesting-code-review