receiving-code-review

Code review feedback should be verified against the actual codebase before implementing any changes. Restate the requirement, check if the suggestion breaks existing behavior or adds unnecessary complexity, and ask clarifying questions for ambiguous items before proceeding.

Pushback on pull request comments requires a reasoned technical response explaining why the suggestion breaks behavior, conflicts with project decisions, or adds unnecessary complexity. Reply directly in the inline comment thread with concise technical justification.

Implement code review changes one item at a time, testing each modification independently. Stop to clarify any ambiguous feedback before moving to the next item, ensuring each change is verified against the codebase and functioning correctly.

Verify reviewer suggestions before writing code whenever the scope is unclear or technically questionable. Read the feedback fully, restate the requirement, and check it against the actual codebase to avoid implementing incorrect or low-value changes.

GitHub pull request review workflows are fully supported, including replying properly in inline comment threads. The process evaluates feedback, verifies against the codebase, and responds with either technical acknowledgment or reasoned pushback.

Code review feedback needs technical rigor to prevent implementing unclear, incorrect, or low-value changes. Blind agreement risks breaking existing behavior or adding unnecessary complexity when reviewer suggestions conflict with project decisions.