receiving-code-review

Receiving Code Review

Core Principle

Technical correctness over performative agreement. Verify feedback before implementing it.

Response Pattern

1. Read the complete feedback.
2. Restate unclear requirements or ask for clarification.
3. Verify each item against the codebase and plan.
4. Evaluate whether the suggestion is correct for this project.
5. Implement one item at a time.
6. Test each fix and report evidence.

Forbidden Responses

• “You’re absolutely right.”
• “Great point.”
• “Excellent feedback.”
• “Let me implement that now” before verification.

Push Back When

• The suggestion breaks existing behavior.
• The reviewer lacks project context.
• The feature is unused or violates YAGNI.
• The feedback conflicts with user decisions.
• You cannot verify the claim.

Output Contract

## Feedback Items
## Clarifications Needed
## Verified Correct
## Pushed Back
## Implemented Fixes
## Verification Evidence