Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
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
# Requesting Code Review
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.
**Core principle:** Review early, review often.
## When to Request Review
**Mandatory:**
- After each task in subagent-driven development
- After completing major feature
- Before merge to main
**Optional but valuable:**
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
## How to Request
**1. Get git SHAs:**
```bash
BASE_SHA=$(git rev-parse HEAD~1) # or: git merge-base origin/main HEAD
HEAD_SHA=$(git rev-parse HEAD)
```
**2. Dispatch code reviewer subagent:**
Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md](code-reviewer.md)
**Placeholders:**
- `{DESCRIPTION}` - Brief summary of what you built
- `{PLAN_OR_REQUIREMENTS}` - What it should do
- `{BASE_SHA}` - Starting commit
- `{HEAD_SHA}` - Ending commit
**3. Act on feedback:**
- Fix Critical issues immediately
- Fix Important issues before proceeding
- Note Minor issues for later
- Push back if reviewer is wrong (with reasoning)
## 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_zovzul3ts2s5fnxz
GET https://markdownregistry.com/api/v1/resolve?ref=sodiumjoe/dotfiles/requesting-code-review
GET https://markdownregistry.com/api/v1/blob/b992457a8918f3d7302506bcf901af6ac57c1ec99a37b13b62779cebd17953f0
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/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
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/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
foryourhealth111-pixel/vibe-skills · bundled/skills/requesting-code-review/SKILL.md · Prepare and request a code review after implementation or before merge by assembling scope, requirements, git range…
a5c-ai/babysitter · library/methodologies/superpowers/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
ganyuanran/aegis · skills/requesting-code-review/SKILL.md · Use when requesting independent code review, after implementation slices, before merging high-risk work, or when…
coco-research/coco · 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/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
