What problem does it solve?
It prevents knee-jerk, performative responses to code review and replaces them with clear understanding, verification against the codebase, and disciplined implementation. This reduces wrong changes, avoids unnecessary features, and aligns fixes with the repository’s actual constraints and your human partner’s priorities.
Core Features & Use Cases
- Structured Review Intake: Read, restate, verify, evaluate, respond, and implement in a strict order to avoid misunderstandings and regressions.
- Clarification-First Workflow: Halt implementation when items are unclear and request targeted clarification before proceeding.
- Context-Aware Pushback: Provide reasoned technical objections when suggestions are incorrect, conflict with architectural decisions, or violate YAGNI.
- Prioritized Implementation: Address blocking/security issues first, then simple fixes, then complex refactors, testing each change.
- Professional-but-Non-Performative Communication: Replace empty praise or apologies with concrete checks, decisions, and results.
Quick Start
Apply the receiving-code-review skill to an incoming review by restating each item, clarifying ambiguities, verifying against the codebase, then implementing and testing changes in priority order while documenting decisions succinctly.
