What problem does it solve? When receiving code review feedback, developers often either blindly implement suggestions or respond with empty agreement. This Skill enforces technical rigor: verify feedback against the actual codebase before implementing, ask clarifying questions when items are unclear, and push back with technical reasoning when suggestions are wrong. ## Core Features & Use Cases - Verification-First Workflow: Read, restate, verify against the codebase, evaluate technical soundness, then respond and implement one item at a time with individual testing. - Source-Based Handling: Treats partner feedback as trusted but still clarifies scope, while external reviewer feedback is checked for correctness, regressions, cross-platform compatibility, and YAGNI violations before implementation. - Structured Pushback and Ordering: Provides rules for when and how to disagree with technical justification, plus an implementation order (blocking issues, simple fixes, complex fixes) with per-item regression testing. - Use Case: A reviewer asks you to delete legacy code. Instead of agreeing, you check build targets, discover the API requires a newer OS version, and respond with the compatibility constraint and a concrete question. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my pull request before implementing anything.
