
Receiving Code Review
When you're on the receiving end of code review feedback, this skill keeps you from either blindly implementing suggestions or getting defensive. It walks you through technical verification before making changes, teaches you how to push back with technical reasoning when reviewers are wrong, and shows you how to ask clarifying questions without the performative "great point!" responses. The pattern is simple: understand the requirement, verify it against your actual codebase, then implement or push back based on technical merit. It's especially useful for handling external reviewers who might not understand your full context.
- skills.sh installs
- 235.1K
- GitHub stars
- 315.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add obra/superpowers --skill receiving-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Files
Code Review Reception
Overview
Code review requires technical evaluation, not emotional performance.
Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.
The Response Pattern
WHEN receiving code review feedback:
1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each
Forbidden Responses
NEVER:
- "You're absolutely right!" (explicit instruction-file violation)
- "Great point!" / "Excellent feedback!" (performative)
- "Let me implement that now" (before verification)
INSTEAD:
- Restate the technical requirement
- Ask clarifying questions
- Push back with technical reasoning if wrong
- Just start working (actions > words)
Handling Unclear Feedback
IF any item is unclear:
STOP - do not implement anything yet
ASK for clarification on unclear items
WHY: Items may be related. Partial understanding = wrong implementation.
Sponsors
Details
- Repository
- github.com/obra/superpowers
- Categories
- Git & Pull Requests, Code Review & Quality
More from obra/superpowers
All 14- Dispatching Parallel Agents231.3K
- Writing Skills231.3K
- Using Git Worktrees230.2K
- Finishing A Development Branch227.7K
- Brainstorming423.3K
- Systematic Debugging326.7K
- Writing Plans298.6K
- Using Superpowers283.7K
- Requesting Code Review276.5K
- Test Driven Development274.8K
- Verification Before Completion270.3K
- Executing Plans257.5K
- Subagent Driven Development252K