receiving-code-review

Code review feedback requires verification against the actual codebase before implementation. You must restate requirements, check codebase reality, push back with evidence on technically questionable revisions, and clarify ambiguity before editing to prevent rushed changes and broken behavior.

Handling ambiguous code review comments requires stopping implementation immediately to resolve the unclear request first. You should restate the requirement, verify it against the codebase, and clarify the ambiguity with the reviewer before writing any code changes.

Pushing back on incorrect code review suggestions requires a technical rigor framework. You verify the reviewer's comment against the codebase reality, then reject unnecessary or incompatible revisions by responding with precise technical reasoning and codebase evidence.

Implementing multiple code review change requests requires an incremental approach. You should implement and test each confirmed change one at a time, ensuring that every individual fix is verified independently to prevent breaking existing behavior.

Reflexive agreement should not be used when processing multi-item change requests, unclear suggestions, or technically questionable revisions. Instead of immediate implementation, you must apply technical rigor, verify feedback, and clarify ambiguity before making any code edits.

This code review response method works with both human and external reviewer comments. It systematically verifies all incoming feedback against the codebase, ensuring technical rigor regardless of the reviewer's origin before any implementation begins.