What problem does it solve?
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Core Features & Use Cases
- Response Pattern: A deterministic workflow to process feedback.
- Six-step process: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
- Handling Unclear Feedback: If any item is unclear, STOP and ask for clarification before proceeding with implementation.
Quick Start
Use the code-review process to respond to feedback:
- READ: Read the feedback in full without reacting.
- UNDERSTAND: Restate the requirement in your own words or ask for clarification.
- VERIFY: Check the feedback against the codebase reality (open PR, touched files, tests).
- EVALUATE: Determine if the requested change is technically sound for THIS codebase.
- RESPOND: Provide a technical acknowledgment or reasoned pushback.
- IMPLEMENT: Implement changes one item at a time and test each.