receiving-code-review

Process code review feedback by reading, understanding, and verifying each suggestion against your codebase before implementing. Evaluate technical soundness, clarify unclear items, and push back with reasoning if feedback conflicts with context or violates YAGNI principles.

Request clarification and verify the feedback against your actual codebase and requirements. Provide technical reasoning to push back on suggestions that are out of context, incomplete, or questionable—don't implement blindly.

Follow a structured protocol: read the feedback, understand its intent, verify it against your code, evaluate its technical merit, respond with your decision and reasoning, then implement one change at a time with tests.

Yes. Reject suggestions that are technically unsound, out of scope, or unnecessary. Explain your reasoning based on codebase reality, architecture decisions, and requirements rather than accepting feedback performatively.

Process feedback one item at a time, verifying and testing each change independently. This prevents bundled mistakes and lets you evaluate and respond to each suggestion on its technical merit.

Verification ensures feedback aligns with your actual codebase, requirements, and architecture. It prevents implementing unclear suggestions, catches out-of-context advice, and maintains code quality through technically rigorous decision-making.