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
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_file: 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:**
```
…
The line at the top of this page pins the label git:20260312.c37221c, 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_6emdxjbzq2qetzl5
GET https://markdownregistry.com/api/v1/resolve?ref=ibrahim-3d/orchestrator-supaconductor/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/ae15c17f29c79b55387106a800c4ca9b7a7789f4d3c826d67ed159d21b71d23d
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.
ibrahim-3d/orchestrator-supaconductor · skills/agent-factory/SKILL.md · Creates specialized worker agents dynamically from templates. Use when orchestrator needs to spawn task-specific…
ibrahim-3d/orchestrator-supaconductor · skills/board-of-directors/SKILL.md · Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices…
ibrahim-3d/orchestrator-supaconductor · skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
ibrahim-3d/orchestrator-supaconductor · skills/business-docs-sync/SKILL.md · Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business…
ibrahim-3d/orchestrator-supaconductor · skills/context-driven-development/SKILL.md · Use this skill when working with Conductor's context-driven development methodology, managing project context…
ibrahim-3d/orchestrator-supaconductor · skills/context-loader/SKILL.md · Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or…
ibrahim-3d/orchestrator-supaconductor · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ibrahim-3d/orchestrator-supaconductor · skills/eval-business-logic/SKILL.md · Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product…
ibrahim-3d/orchestrator-supaconductor · skills/eval-code-quality/SKILL.md · Specialized code quality evaluator for the Evaluate-Loop. Use this for evaluating code implementation tracks where the…
obra/superpowers · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
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…
coco-research/coco · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
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…
iliaal/ai-skills · skills/receiving-code-review/SKILL.md · Process code review feedback critically: check correctness before acting, push back on incorrect suggestions, no…
