Requesting Code Review

Requesting Code Review is a Superpowers skill for preparing a review request with enough context for another reviewer or agent to evaluate the actual change. It connects the implementation, requirements and relevant git diff so feedback can focus on correctness and risk rather than guessing what the code was meant to do.

• Developers requesting AI-assisted review before merge
• Teams using subagents for independent code review
• Engineers preparing a focused pull-request review
• Workflows that separate implementation from verification

• Ask a reviewer to compare a change with its requirements
• Review a specific commit range before merge
• Catch issues before moving to the next implementation task
• Provide code context without dumping an entire repository

The skill identifies the implemented task, requirements and commit range, then dispatches or prepares a focused review request around that scope. It is commonly paired with staged development workflows where review happens at defined checkpoints rather than only at the end.

• Gives reviewers the intent and change scope they need
• Supports independent verification in agent workflows
• Makes review more repeatable between tasks
• Reduces low-value feedback caused by missing context

• A well-structured request does not guarantee a high-quality review
• The reviewer still needs appropriate repository and requirement context
• Very large changes may need to be split into smaller reviewable units