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. **Core principle:** Review early, review often. ## When to Request Review **Mandatory:** - At the final gate of the subagent path, once, over the whole branch — the review after each task there runs a different instrument, [task-reviewer-prompt.md](../subagent-driven-development/task-reviewer-prompt.md) - After completing major feature - Before merge to main — and superpowersplus:final-branch-audit runs BEFORE this review, not after: a reviewer judges the diff it is handed, and a task nobody implemented produces no diff to judge. **Optional but valuable:** - When stuck (fresh perspective) - Before refactoring (baseline check) - After fixing complex bug ## How to Request **1. Get git SHAs:** ```bash # Never HEAD~1: a task with more than one commit loses all but the last, # silently. Use the BASE recorded before the work started, or the fork point. BASE_SHA=$(git merge-base <base-branch> HEAD) HEAD_SHA=$(git rev-parse HEAD) ``` **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 Cri