Respond to Code Review
Treat review comments as hypotheses and decisions to evaluate, not commands that automatically override current evidence.
Workflow
- Capture every comment with its author, location, revision, requested outcome, and whether it is still current.
- Restate the technical claim and inspect the relevant code, contract, test, or platform evidence.
- Classify the comment as
accept,reject,defer,clarify, oralready addressed, with evidence. - Resolve conflicting feedback by identifying the governing requirement or decision owner.
- Implement accepted in-scope changes only when the user authorized implementation.
- Add regression evidence for defect claims and rerun affected gates.
- Prepare concise responses that explain evidence, changes, and remaining uncertainty.
- Send responses or resolve threads only when that external write is authorized.
Boundaries
- Do not accept feedback merely because it sounds authoritative.
- Do not dismiss feedback without checking the actual claim.
- Do not resolve a thread as a substitute for implementing or verifying the agreed change.
- Review approval, passing checks, merge, and deployment remain separate states.
Output
Return a table with Comment, Verdict, Evidence, Action, and Response, followed by validation and unresolved decisions.