Receive Code Review
Process incoming code review feedback with technical rigor. Verify each finding against the actual code before agreeing. Distinguish valid findings from misreadings. Implement only confirmed findings. Do not perform blind, sycophantic agreement — that's as harmful as ignoring review.
| Name | Type | Description |
|---|---|---|
review_feedback | string | The review comments or findings to process. |
diff optional | string | The original diff the review was made against. |
| Name | Type | Description |
|---|---|---|
finding_responses | array | Per-finding response: valid/invalid/clarification-needed, with evidence and action taken. |
- may write files (implementing valid findings)
- may create commits
Process code review feedback with rigor. For each finding: (1) Read the cited code. (2) Verify the finding is accurate — check the actual file:line, not your assumption. (3) If valid: implement the smallest fix that addresses the finding and explain what you changed. (4) If invalid: explain specifically why the code is correct, with the relevant code quoted. (5) If unclear: ask for clarification before implementing. Never agree sycophantically without verifying. Never rewrite sections not cited in the review. One commit per review finding.