requesting-code-reviewlisted

# 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. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work. **Core principle:** Review early, review often. ## When to Request Review **Mandatory:** - After each task in spec-driven development (`/spec:execute`) - After completing a major feature - Before merge to main **Optional but valuable:** - When stuck (fresh perspective) - Before refactoring (baseline check) - After fixing a complex bug ## Lightweight Alternative For quick self-review without dispatching a subagent, use `/review-recent-work`. This traces through recently modified functions to verify correctness and completeness inline. Use the full code-reviewer subagent (below) for deeper, more rigorous review. ## How to Request ### 1. Get git SHAs ```bash BASE_SHA=$(git rev-parse HEAD~1) # or origin/main for full branch review HEAD_SHA=$(git rev-parse HEAD) ``` ### 2. Dispatch code-reviewer subagent Use the Task tool with `code-reviewer` type. Supply the following context: **Required context:** - `{WHAT_WAS_IMPLEMENTED}` — What you just built - `{PLAN_OR_REQUIREMENTS}` — What it should do (spec path, task description, or requirements) - `{BASE_SHA}` — Starting commit - `{HEAD_SHA}` — Ending commit - `{DESCRIPTION}` — Brief summary of the changes *