requesting-code-reviewlisted

<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Requesting Code Review Dispatch a code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context — never your session history — so it stays focused on the work product, not your thought process, and your own context is preserved. **Core principle:** Review early, review often. ## Fits in the pipeline The mechanism behind the **Stage 7 per-feature QA gate** — the four lenses (security-engineer, code-quality-reviewer, adversarial-tester, qa-engineer) are dispatched this way — and the final review in **Stage 8**. Inside `subagent-driven-development` it runs after every task. Priority: **user > skills > default**; `_shared/vibegod-principles.md` apply. Reviewers must include the consistency/no-orphans check (principle #6) — see `verification-before-completion`. ## When to Request Review **Mandatory:** after each task in subagent-driven development; after a major feature; before merge to main. **Optional but valuable:** when stuck (fresh perspective); before refactoring (baseline check); after fixing a complex bug. ## How to Request **1. Get git SHAs:** ```bash BASE_SHA=$(git rev-parse HEAD~1) # or origin/main HEAD_SHA=$(git rev-parse HEAD) ``` **2. Dispatch a code-reviewer subagent** (Task tool, general-purpose). Give it exactly: - **Description** — brief summary of what you built. - **Plan/requirements** — what it should do (link