receiving-code-review

Validating code-review feedback involves cross-checking comments against codebase constraints and existing tests. This process identifies unclear items, prompts clarifying questions, and ensures technical reasoning confirms correctness, compatibility, and safety before safely applying changes.

Handling ambiguous code-review comments requires a clarification workflow that identifies unclear items and prompts for specific questions. This prevents misinterpretation by cross-checking feedback against project reality rather than blindly agreeing and implementing without validation.

Implementing multiple code-review feedback items safely requires staged implementation, tackling each item one at a time with testing and validation. This rigorous process checks for correctness, compatibility, and safety before applying changes to prevent regressions.

Clarifying code-review feedback before writing code prevents misinterpretation and avoids blindly implementing changes without validation. Technical verification cross-checks feedback against codebase constraints and existing tests to ensure accurate understanding and safe application.

Pushing back on code-review feedback is appropriate when technical verification shows conflicts with existing tests or codebase constraints. The process guides reasoning about technical implications and validating correctness, compatibility, and safety before applying any changes.

You should not apply code-review feedback directly when items are unclear or unverified. Skipping the clarification workflow and technical verification against codebase constraints risks misinterpretation and unsafe changes, bypassing checks for correctness, compatibility, and safety.