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
Install
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/receiving-code-review ~/.claude/skills/receiving-code-reviewFrom README
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.
More from this repo
systematic-debugging
Used when encountering any bug, test failure, or unexpected behavior, before proposing fixes
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying...
dispatching-parallel-agents
Used when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies