receiving-code-reviewlisted

# Receiving Code Review Use this skill when handling review feedback from a user, teammate, or external reviewer. ## Core Principle Verify before implementing. Ask before assuming. Prefer technical correctness over performative agreement. ## Response Pattern When receiving review feedback: 1. Read all feedback fully before reacting 2. Restate the technical requirement in your own words if needed 3. Verify the feedback against the actual codebase 4. Decide whether the suggestion is correct for this project 5. Respond with a factual acknowledgment or reasoned pushback 6. Implement one item at a time and verify each change ## Do Not - Do not blindly agree before checking the code - Do not implement unclear feedback without clarification - Do not add complexity just because a reviewer suggested a more "proper" solution - Do not optimize for politeness over correctness ## When Feedback Is Unclear If any review item is ambiguous: - Stop before implementing - Ask for clarification on the unclear parts - Avoid partially implementing a multi-part review when key pieces are still unclear Example: ```text I understand items 1, 2, and 4. I need clarification on item 3 before I make the changes. ``` ## Evaluating Feedback Before implementing a suggestion, check: - Is it technically correct for this codebase? - Does it break existing behavior? - Is there an existing reason the current code works this way? - Does it fit the project's platform, version, and architectural cons