What problem does it solve? Receiving code review feedback often leads to two failure modes: performative agreement without verification, or blind implementation of suggestions that may break the codebase. This Skill enforces a disciplined response pattern where every piece of feedback is read, understood, verified against the actual codebase, and only then implemented or pushed back on with technical reasoning. ## Core Features & Use Cases - Structured Response Pattern: Defines a six-step flow (read, understand, verify, evaluate, respond, implement) for handling any review feedback. - Source-Specific Handling: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skepticism and verification. - YAGNI and Pushback Rules: Checks whether suggested features are actually used in the codebase and provides guidance for reasoned pushback when suggestions are wrong. - Use Case: A reviewer asks you to remove legacy code. Instead of agreeing immediately, you check build targets, discover the code is needed for backward compatibility, and respond with the technical constraint plus options. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before implementing any changes.
