Code Review Reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Install
npx skills add obra/clank --skill Code Review Receptiongit clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/collaboration/receiving-code-review ~/.claude/skills/Code-Review-ReceptionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Reception ## Overview Code review requires technical evaluation, not emotional performance. **Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort. ## The Response Pattern ``` WHEN receiving code review feedback: 1. READ: Complete feedback without reacting 2. UNDERSTAND: Restate requirement in own words (or ask) 3. VERIFY: Check against codebase reality 4. EVALUATE: Technically sound for THIS codebase? 5. RESPOND: Technical acknowledgment or reasoned pushback 6. IMPLEMENT: One item at a time, test each ``` ## Forbidden Responses **NEVER:** - "You're absolutely right!" (explicit CLAUDE.md violation) - "Great point!" / "Excellent feedback!" (performative) - "Let me implement that now" (before verification) **INSTEAD:** - Restate the technical requirement - Ask clarifying questions - Push back with technical reasoning if wrong - Just start working (actions > words) ## Handling Unclear Feedback ``` IF any item is unclear: STOP - do not implement anything yet ASK for clarification on unclear items WHY: Items may be related. Partial understanding = wrong implementation. ``` **Example:** ``` your human partner: "Fix 1-6" You understand 1,2,3,6. Unclear on 4,5. ❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later ✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding." ``` ## Source-Specific Handling ### From your human partner
Details
- Skill name
Code Review Reception- Repository
- obra/clank
- Path
skills/collaboration/receiving-code-review/SKILL.md- Repo updated
- 9 October 2025
FAQ
What does the Code Review Reception skill do?
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
How do I install the Code Review Reception skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Code Review Reception. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Review Reception popular?
It lives in obra/clank, which has 43 GitHub stars and 26 forks.
Related skills
Gardening Skills Wiki
43obra/clank
Maintain skills wiki health - check links, naming, cross-references, and coverage
Remembering Conversations
43obra/clank
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Brainstorming Ideas Into Designs
43obra/clank
Interactive idea refinement using Socratic method to develop fully-formed designs
Contribute
43inite-ai/inite-brain-service
Take an idea for INITE Brain from plain words to a green pull request. Use when someone says "I have an idea", "I want to add / change / fix something in Brain", "make Brain do X", or asks how to contribute — engineer or not.
Careful Delete
62ElliotJLT/Claude-Skill-Potions
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
Finishing a Development Branch
43obra/clank
Complete feature development with structured options for merge, PR, or cleanup
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.