staff-receiving-code-review

To evaluate code review feedback, verify each comment against the actual codebase, test changes one at a time, and push back with technical reasoning if suggestions break behavior or violate YAGNI.

When a pull request comment is unclear or incomplete, you should stop and ask the reviewer for clarification before making any changes to ensure you understand the exact intent.

To push back on questionable code review suggestions, respond with precise technical reasoning detailing why the change would break behavior, violate YAGNI, or ignore architectural context.

To handle conflicting feedback items in a pull request, evaluate each suggestion individually against the codebase, identify the conflicts, and request clarification to resolve the contradictions before implementation.

You should not implement multiple code review changes at the same time; instead, apply one-at-a-time tested changes to isolate behavior verification and ensure each modification works exactly as intended.