What problem does it solve? Code review feedback often gets implemented blindly or acknowledged with empty agreement, leading to broken functionality, wasted effort on unused features, and regressions. This Skill enforces a verify-before-implement discipline so every review comment is checked against the actual codebase before any change is made. ## Core Features & Use Cases - Structured Response Pattern: Read, restate, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Treats user feedback as trusted but scope-checked, while external reviewer suggestions are validated for correctness, compatibility, and conflicts with prior architectural decisions. - YAGNI and Pushback Rules: Greps the codebase for actual usage before accepting "implement properly" suggestions, and pushes back with technical reasoning when feedback is wrong. - TDD Per Verified Item: Applies red-green-refactor to each confirmed change through public interfaces, skipping TDD only for docs or config changes. - Use Case: A reviewer on a GitHub pull request asks you to remove legacy code and add a metrics endpoint. You verify the legacy code is still required for backward compatibility, find no callers for the metrics endpoint, push back with evidence, and reply in the inline comment thread. ## Quick Start Use the receiving-code-review skill to evaluate the review comments on this pull request and implement only the verified items one at a time.
