requesting-code-review

Dispatch superpowers: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. Mandatory: Optional but valuable: 1. Get git SHAs: 2. Dispatch code-reviewer subagent: Use Task tool with superpowers:code-reviewer type, fill template at code-reviewer.md Placeholders: 3. Act on feedback: Subagent-Driven Development: Executing Plans: Ad-Hoc Development: Never: If reviewer wrong: See template at: requesting-code-review/code-reviewer.md - After each task in subagent-driven development - After completing major feature - Before merge to main - When stuck (fresh perspective) - Before refactoring (baseline check) - After fixing complex bug - {WHAT_WAS_IMPLEMENTED} - What you just built - {PLAN_OR_REQUIREMENTS} - What it should do - {BASE_SHA} - Starting commit - {HEAD_SHA} - Ending commit - {DESCRIPTION} - Brief summary - Fix Critical issues immediately - Fix Important issues before proceeding - Note Minor issues for later - Push back if reviewer is wrong (with reasoning) - Review after EACH task - Catch issues before they compound - Fix before moving to next task - Review after each batch (3 tasks) - Get feedback, apply,...