What problem does it solve?
Help developers process and respond to code review feedback in a way that prioritizes technical correctness over performative agreement, prevents blind implementation, and avoids regressions caused by misunderstood or incorrect suggestions.
Core Features & Use Cases
- Structured Response Pattern: Read full feedback, restate requirements, verify against the codebase, evaluate technical correctness, acknowledge or push back, then implement and test each item.
- Source-Aware Handling: Differentiate between trusted human partners and external reviewers, applying extra verification for external suggestions and stopping to consult the human partner on conflicts.
- Risk-Based Implementation Order: Clarify unclear items first, then fix blocking/security issues, simple fixes, and finally complex refactors, testing each change to avoid regressions.
- Use Case: When a PR receives a mixed set of inline comments from maintainers and external reviewers, use this Skill to triage, verify, and respond with technical acknowledgments or reasoned pushback rather than performing immediate changes.
Quick Start
Restate unclear review items, verify each suggestion against the codebase and tests, ask for clarification when needed, and implement fixes one at a time ordered by severity while providing concise technical acknowledgments or reasoned pushback.