requesting-code-review
obra/superpowers
Dispatch a code reviewer subagent to catch issues before they cascade.
What is requesting-code-review?
Request focused code review from a subagent reviewer with precisely crafted context about your changes. Use after completing tasks, implementing major features, or before merging to verify work meets requirements and catch issues early.
- Dispatch a general-purpose subagent configured as a code reviewer
- Pass targeted context (description, requirements, git SHAs) without exposing session history
- Receive structured feedback categorized by severity (Critical, Important, Minor)
- Maintain clean separation between coordinator context and reviewer evaluation
- Preserve coordinator context window for continuing work after review
How to install requesting-code-review
npx skills add https://github.com/obra/superpowers --skill requesting-code-review- Git repository with commit history
- Ability to dispatch general-purpose subagents
- Access to code-reviewer.md template
How to use requesting-code-review
- 1.Get the base and head git SHAs using git rev-parse or git merge-base
- 2.Dispatch a general-purpose subagent with the code-reviewer.md template
- 3.Fill in DESCRIPTION (what you built), PLAN_OR_REQUIREMENTS (requirements), BASE_SHA, and HEAD_SHA placeholders
- 4.Receive feedback from reviewer subagent categorized by severity
- 5.Fix Critical issues immediately, Important issues before proceeding, and note Minor issues for later
- 6.Push back with technical reasoning if reviewer feedback is incorrect
Use cases
- After completing each task in subagent-driven development to verify correctness
- Before merging to main branch to catch integration issues
- When stuck on implementation to get fresh perspective from reviewer
- Before major refactoring to establish baseline code quality
- After fixing complex bugs to ensure fix is sound and complete
- Developers using subagent-driven development workflows
- Teams practicing continuous code review
- Coordinators managing multiple subagent tasks
- Anyone wanting to preserve context window while getting external review
requesting-code-review FAQ
You're the coordinator—reviewing inline burns the context window you need to keep driving work. The subagent keeps diff analysis and evaluation in its own context, returning only findings to you.
No. Hand it precisely crafted context (description, requirements, git SHAs) instead. This keeps the reviewer focused on the work product, not your thought process.
After each task in subagent-driven development, after completing major features, and before merging to main. Optional but valuable: when stuck, before refactoring, or after fixing complex bugs.
Push back with technical reasoning, show code or tests that prove it works, or request clarification. Never ignore valid technical feedback, but don't accept invalid feedback either.
No. Never skip review because 'it's simple.' Early, frequent review catches issues before they cascade.
Full instructions (SKILL.md)
Source of truth, from obra/superpowers.
name: requesting-code-review description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Requesting Code Review
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.
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:
BASE_SHA=$(git rev-parse HEAD~1) # or: git merge-base origin/main HEAD
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch code reviewer subagent:
Dispatch a general-purpose subagent, filling the template at code-reviewer.md
Placeholders:
{DESCRIPTION}- Brief summary of what you built{PLAN_OR_REQUIREMENTS}- What it should do{BASE_SHA}- Starting commit{HEAD_SHA}- Ending commit
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
[Just completed Task 2: Add verification function]
You: Let me request code review before proceeding.
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch code reviewer subagent]
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
[Subagent returns]:
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Ready to proceed
You: [Fix progress indicators]
[Continue to Task 3]
Common Rationalizations
| Excuse | Reality |
|---|---|
| "I'll just review the diff myself instead of dispatching a reviewer" | You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. |
| "The reviewer needs my whole session history to understand the change" | Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. |
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: code-reviewer.md
Related skills
More from obra/superpowers and the wider catalog.
