Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Requesting Code Review Dispatch superpowers:code reviewer subagent to catch issues before they cascade. Core principle: Review early, review often. When to Request Review 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 How to Request 1. Get git SHAs: 2. Dispatch code reviewer subagent: Use Task tool with superpowers:code reviewer type, fill template at code reviewer.md Placeholders: {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 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) Example Integration with Workflows 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 Red Flags Never: Skip review because "it's simple" Ignore Critical issues Proceed with unfixed Important issues Argue with valid technical feedback If reviewer wrong: Push back with technical reasoning Show code/tests that prove it works Request clarification See template at: requesting code review/code reviewer.md When to Use This skill is applicable to execute the workflow or actions described in the overview. Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

requesting-code-review