What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a disciplined response pattern: verify feedback against the codebase before implementing, ask for clarification on unclear items, and push back with technical reasoning when suggestions are wrong. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including YAGNI checks for unused features. - Pushback and Correction Guidance: Concrete scripts for disagreeing with reviewers using technical reasoning and for gracefully correcting your own wrong pushback. - Use Case: A reviewer asks you to remove legacy code. Instead of agreeing immediately, you check the build target, discover the API requires a newer OS version, and respond with the compatibility constraint and a question about dropping old platform support. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my pull request before implementing any changes.
