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 so feedback is evaluated against the actual codebase before any change is made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skeptical verification. - Pushback and YAGNI Checks: Provides rules for pushing back with technical reasoning and checking whether suggested features are actually used before implementing them. - Use Case: A reviewer asks you to remove legacy code. Instead of agreeing immediately, you verify the build target and discover the legacy path is required for backward compatibility, then reply with that technical reasoning. ## Quick Start Apply the receiving-code-review skill to evaluate the reviewer comments on my pull request before implementing any changes.
