Optimizes code review interactions by prioritizing technical verification and rigor over performative agreement.
The Receiving Code Review skill establishes a disciplined framework for Claude to process feedback with technical skepticism. It replaces social filler and blind implementation with a structured protocol: reading without reaction, restating requirements, verifying against the codebase, and evaluating technical soundness. By enforcing the 'verify before implementing' principle, this skill ensures that code changes are necessary, correct, and aligned with existing architectural patterns while explicitly avoiding unproductive 'thank you' loops and social performance.
Key Features
01Context-aware handling for both trusted partners and external reviewers
02YAGNI (You Ain't Gonna Need It) checks for new feature requests
03Strict prohibition of performative agreement and gratitude expressions
04Mandatory technical verification protocol for all incoming suggestions
053 GitHub stars
06Structured pushback logic for technically incorrect or conflicting feedback
Use Cases
01Processing complex multi-item feedback from a lead developer with technical clarity
02Critically evaluating suggestions from external automated tools or third-party reviewers
03Ensuring new feature suggestions are actually utilized in the codebase before implementation
