What problem does it solve? When receiving code review feedback, it is easy to either blindly implement every suggestion or respond with performative agreement instead of technical evaluation. This Skill enforces a disciplined workflow: read, understand, verify against the actual codebase, then implement or push back with reasoning. ## Core Features & Use Cases - Structured Response Pattern: Walks through six steps — read, understand, verify, evaluate, respond, implement — so no feedback item is acted on without verification. - Pushback Guidance: Defines when and how to disagree with a reviewer using technical reasoning, including YAGNI checks and conflicts with prior architectural decisions. - Unclear Feedback Handling: Requires clarifying ambiguous items before implementing anything, preventing partial-understanding mistakes. - Use Case: A reviewer suggests refactoring a function and adding error handling. Before changing code, you grep for actual call sites, find the suggestion would break an existing caller, and respond with reasoned pushback instead of a breaking change. ## Quick Start Apply the receiving-code-review skill to evaluate the reviewer comments on my pull request before I implement any changes.
