This is for when you get code review feedback and need to actually think through whether the suggestions make sense before blindly implementing them. It pushes you to verify feedback against the actual codebase, ask clarifying questions when something's unclear, and push back with technical reasoning if a reviewer's wrong or missing context. The core idea is stop the performative "great point!" responses and focus on technical correctness over social comfort. Includes specific workflows for handling ambiguous feedback, YAGNI checks for over-engineered suggestions, and rules for when to push back on external reviewers versus trusted collaborators. Honestly refreshing to see a skill that treats code review as technical evaluation rather than emotional theater.
npx skills add https://github.com/jnmetacode/superpowers-zh --skill receiving-code-review