What problem does it solve? Engineers and AI agents often respond to code review feedback with performative agreement or blind implementation, shipping unverified changes that break functionality or miss sibling occurrences of the same defect. This Skill enforces technical verification, clarification of unclear items, and complete pattern propagation before any code changes. ## Core Features & Use Cases - Verify-Before-Implement Workflow: A six-step response pattern (read, understand, verify, evaluate, respond, implement) that replaces performative agreement with technical rigor. - Pattern Propagation Check: Sweeps the current PR diff for sibling occurrences of each accepted finding, including analogous paths (CLI vs MCP, primary vs fallback, sync vs async) and shared-helper call sites. - Proportionality Gate: Decides whether an accepted finding gets fixed now or filed as a follow-up ticket based on fix complexity and cumulative PR size. - Use Case: A reviewer flags a missing nil check in one handler; the Skill directs you to fix the same defect in the other two handlers the PR touched, verify shared-helper callers, and reply in each GitHub comment thread. ## Quick Start Use the receiving-code-review skill to process the reviewer feedback on my current pull request before making any changes.
