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 instruction-file 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 v1.0.1, 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_qbugy3m6z7wxaltv
GET https://markdownregistry.com/api/v1/resolve?ref=sodiumjoe/dotfiles/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/35260492c5e0f54e51ff6378239f4ff6e5fe5f95d7d71982965e62c33507ca28
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.
sodiumjoe/dotfiles · home/.agents/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
sodiumjoe/dotfiles · home/.agents/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
sodiumjoe/dotfiles · home/.agents/skills/executing-plans/SKILL.md · Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose…
sodiumjoe/dotfiles · home/.agents/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
sodiumjoe/dotfiles · home/.agents/skills/neovim-review/SKILL.md · Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.
sodiumjoe/dotfiles · home/.agents/skills/neovim/SKILL.md · Interact with a running neovim instance over RPC — open files, show diffs, execute Lua. Use when you need to open a…
sodiumjoe/dotfiles · home/.agents/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
sodiumjoe/dotfiles · home/.agents/skills/subagent-driven-development/SKILL.md · Use when executing implementation plans with independent tasks in the current session
sodiumjoe/dotfiles · home/.agents/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
sodiumjoe/dotfiles · home/.agents/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
sodiumjoe/dotfiles · home/.agents/skills/using-git-worktrees/SKILL.md · Use when starting feature work that needs isolation from current workspace or before executing implementation plans -…
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…
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…
