receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Before you install
- Last update
- Files in folder
- 1
- Scripts
- No script files found
- SKILL.md size
- 6.1 KB (about 1,551 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- obra/superpowers
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add obra/superpowers@receiving-code-reviewRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add obra/superpowers@receiving-code-review --agent claude-code -y- Project install writes to
.claude/skills/receiving-code-review- Global install writes to
~/.claude/skills/receiving-code-review
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /receiving-code-review.
What it does
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 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…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Categories
Related skills
- brainstorming
obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
- systematic-debugging
obra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- writing-plans
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
- using-superpowers
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
265K installs 301K - requesting-code-review
obra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- verification-before-completion
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always