Receiving code review

Mindset

• Reviewers surface risk you may have missed; treat feedback as input, not orders.
• Verify technical claims before changing code (read code, run tests).

Workflow

1. Read fully — understand intent, not only the literal suggestion.
2. Clarify — if feedback is vague, ask one focused question before partial implementation.
3. Verify — reproduce issue or confirm the concern in code; do not assume the reviewer is correct.
4. Prioritize — correctness and security before style.
5. Respond — agree + fix, or disagree with evidence (snippet, test, spec).
6. Batch related fixes; avoid drive-by changes outside review scope.
7. Confirm — run verification before marking threads resolved.

When to push back