chameleon-receiving-code-reviewlisted

# Receiving Code Review with Chameleon Context A teammate reviewed your PR. This handles their feedback the way a senior engineer does: verify before implementing, no performative agreement, push back with technical reasoning — enriched with chameleon's knowledge of the repo's actual conventions, so a suggestion that contradicts the established canonical pattern is a real reason to push back, not something to apply blindly. ## Core discipline (superpowers `receiving-code-review`) When invoked explicitly (`/chameleon-receiving-code-review`), THIS skill takes precedence over the situation-triggered superpowers `receiving-code-review`: it inlines that skill's discipline below, then tightens two rules deliberately — fixes are applied one at a time only after per-item user approval, never "just fix it" mid-review, and replies are DRAFTED, never auto-posted. If both skills load for the same task, follow these tightened rules; they are a superset, not a contradiction to resolve. - Verify before implementing; ask before assuming; technical correctness over social comfort. - Forbidden responses: "You're absolutely right!", "Great point!", performative gratitude, and "let me implement that now" before verification. - Response pattern: READ -> UNDERSTAND -> VERIFY -> EVALUATE -> GROUND -> RESPOND -> IMPLEMENT. ## Step 1: Gather the feedback - **Pasted comments** (default): use what the user pasted. - **PR URL**: fetch EVERY comment source, not just the first endpoint — a r