receiving-code-review

Evaluate code review feedback by verifying technical correctness, scope clarity, and codebase reality before acting. Check reviewer suggestions against existing implementation, request clarification on ambiguous items, and apply one-at-a-time fixes with testing to avoid incorrect changes and wasted iteration.

Handle ambiguous pull request comments by stopping immediately and asking the reviewer for precise clarification. Do not attempt changes until the scope and intent of the feedback are clear, ensuring technical rigor and preventing incorrect modifications to the codebase.

Push back on conflicting code review suggestions using evidence-based validation against the actual codebase. Verify technical correctness first, provide concrete evidence from the existing implementation, and maintain regression awareness while addressing each review item one at a time.

Process multi-item review threads sequentially by isolating each fix, validating the change, and testing for regressions before moving to the next comment. This safe implementation workflow maintains technical rigor and prevents compounding errors across inline reviewer comments.

Verify code review feedback to avoid performative agreement and ensure technical correctness. Reviewers can miss codebase context or suggest unsound changes, so checking suggestions against existing implementation prevents incorrect changes, scope creep, and wasted iteration cycles.

This approach works for inline reviewer comments, multi-item review threads, and general pull request feedback. It evaluates technical correctness, scope clarity, and codebase reality across all review formats, requiring clarification and evidence-based pushback where needed before any implementation begins.