Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Code Review Reception
## Overview
**Announce at start:** "Receiving Code Review skill activated."
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
…
The line at the top of this page pins the label git:20260802.1479e32, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_mxotrjiwfawtrq4n
GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/f1d26c7ccf0ad8e3fd188871570e197888d1f82a805ade6881972af43cbcd710
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
coco-research/coco · adapters/cursor/skills/create-rule/SKILL.md · Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up…
coco-research/coco · adapters/cursor/skills/create-skill/SKILL.md · Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a…
coco-research/coco · adapters/cursor/skills/create-subagent/SKILL.md · Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up…
coco-research/coco · adapters/cursor/skills/update-cursor-settings/SKILL.md · Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences…
coco-research/coco · skills/agent-lightning/SKILL.md · Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting…
coco-research/coco · skills/agent-self-eval/SKILL.md · Post-run self-evaluation system that scores agent output on correctness, clarity, actionability, and conciseness. Use…
coco-research/coco · skills/ai-product/SKILL.md · Use when building AI features into a product: LLM integration, RAG pipelines, guardrails, streaming, AI UX, prompt…
coco-research/coco · skills/api-design-principles/SKILL.md · Use when designing a new REST or GraphQL API, reviewing an API spec before implementation, setting team API standards…
obra/superpowers · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
foryourhealth111-pixel/vibe-skills · bundled/skills/receiving-code-review/SKILL.md · Review-feedback handling route for CodeRabbit, GitHub, PR, or human reviewer comments. Use before implementing…
a5c-ai/babysitter · library/methodologies/superpowers/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification…
ganyuanran/aegis · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
jamditis/claude-skills-journalism · superjawn/skills/receiving-code-review/SKILL.md · Verifies review feedback with technical rigor, not blind agreement. Use when receiving review before implementing…
ibrahim-3d/orchestrator-supaconductor · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…