requesting-code-review

Topics in the source

• Requesting Code Review
• When to Request Review
• How to Request
• Example
• Integration with Workflows
• Red Flags

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. Core principle: Review early, review often. 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 1. Get git SHAs: 2. Dispatch code-reviewer subagent: Use Task tool with superpowers:code-reviewer type, fill template at code-reviewer.md Placeholders: {WHATWASIMPLEMENTED} - What you just built {PLANORREQUIREMENTS} - What it should do {BASESHA} - Starting commit {HEADSHA} - Ending commit {DESCRIPTION} - Brief summary 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) Subagent-Driven Development: Review after EACH task Catch issues before they compound Fix before moving to next task Executing Plans: Review after each batch (3 tasks) Get feedback, apply, continue Ad-Hoc Development: Review before merge Review when stuck Never: Skip review because "it's simple" Ignore Critical issues Proceed with unfixed Important issues Argue

This is an excerpt. Refer to the complete source and its current requirements.