This file is byte-identical to the first copy the registry indexed, one of 8 indexed copies. Same content hash, so the same checks give both the same grade.
receiving-code-review from xu123-bob/baize is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
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: 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:20260912.5e131e8, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6314 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
xu123-bob/baize · 590 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ik3os7bsk6twpn7d
GET https://markdownregistry.com/api/v1/resolve?ref=xu123-bob/baize/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/c9382e92b8f32363566068ecfed19d3b2651eaf40d3942b24840f839dedfc406
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.
xu123-bob/baize · agent/skills/impeccable-skill-v3.9.1/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/subagent-driven-development/SKILL.md · Use when executing implementation plans with independent tasks in the current session
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/using-git-worktrees/SKILL.md · Use when starting feature work that needs isolation from current workspace or before executing implementation plans -…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/using-superpowers/SKILL.md · Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
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…
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…
julianromli/ai-skills · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…