receiving-review

Structured clarification involves prompting the reviewer for details on unclear feedback before coding. Technical verification then cross-checks that feedback against the codebase and tests to ensure the suggested changes are technically sound.

Incremental changes involve implementing one code review item at a time with validation. This engineering process ensures guarded implementation, reduces defects, and allows you to verify each change against the repository before proceeding.

This code review skill handles incoming pull request feedback by applying rigorous technical verification across the codebase. It satisfies the need for clear questioning, controlled changes, and guarded implementation to reduce defects and misinterpretations.

Code review feedback may be technically questionable or unclear, requiring rigorous verification across the codebase. If the suggested changes cannot be easily validated against existing tests, you should request clarification before proceeding.

Code review feedback should be avoided when it lacks clarity or technical accuracy. If feedback cannot be rigorously verified against the codebase and tests, requesting clarification is required to prevent performative agreement and implementation defects.