receiving-code-review

Handle code review feedback by evaluating each item for correctness and non-regressions before implementing changes. Use a structured workflow to read, verify, and evaluate suggestions against project guidelines, logging decisions to ensure technical rigor.

Push back on unclear code review comments by pausing to ask for clarification first. If a recommendation is potentially harmful, provide a reasoned technical explanation detailing why the proposed changes are not correct for the current codebase.

Structure a decision log for code review changes by documenting each feedback item's evaluation, verification results, and alignment with project guidelines. This disciplined process tracks whether changes were implemented, clarified, or rejected with technical pushback.

Ask for clarification during a code review immediately when any feedback item is unclear. This clarification-first handling approach prevents incorrect changes and ensures you understand the requirements before attempting any code modifications.

Verify technical feedback before implementing code changes by applying a disciplined verification process. Check that suggestions ensure correctness, avoid non-regressions, and align with project guidelines, maintaining a clear decision log throughout the evaluation.