What problem does it solve? When receiving code review feedback, AI agents and developers often default to performative agreement or blind implementation, which leads to regressions, unnecessary features, and unverified changes. This Skill enforces a disciplined response pattern that requires technical verification before any code change. ## Core Features & Use Cases - Six-Step Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Pushback and YAGNI Checks: Push back on technically incorrect suggestions with reasoning, and grep the codebase to reject unused feature requests. - Source-Specific Handling: Apply different trust levels for feedback from your human partner versus external reviewers, including GitHub inline thread replies via the gh API. - Use Case: A reviewer leaves six PR comments, two of which are unclear and one suggesting an unused endpoint be built out. The Skill instructs you to clarify the unclear items first, verify each claim against the codebase, and propose removing the unused endpoint instead of implementing it. ## Quick Start Use the receiving-code-review skill to process the reviewer comments on my current pull request before making any changes.
