Review Feedback

Review feedback is a claim to evaluate, not an instruction to obey. Verify first, then decide with evidence.

1. Read the whole review

Read all feedback before changing code. Include earlier review rounds and related fixes. Group comments that may be symptoms of the same invariant, owner, or boundary.

If an unclear item changes how coupled items should be handled, ask one precise question and wait. Otherwise continue evaluating independent items.

2. Verify the claim

Open the cited code and trace the real path. Reproduce the issue or run the closest existing test when possible. Check requirements, project conventions, target versions, history, and current behavior rather than generic best practice.

Before expanding scope, search for actual callers, users, and specifications. No demand may mean the right change is deletion, not a more elaborate implementation.

3. Choose the right layer

For every verified issue, compare: