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
# Pre-Commit Code Verification
Automated verification pipeline before code lands. Static scans, baseline-aware
quality gates, an independent reviewer subagent, and an auto-fix loop.
**Core principle:** No agent should verify its own work. Fresh context finds what you miss.
## When to Use
- After implementing a feature or bug fix, before `git commit` or `git push`
- When user says "commit", "push", "ship", "done", "verify", or "review before merge"
- After completing a task with 2+ file edits in a git repo
- After each task in subagent-driven-development (the two-stage review)
**Skip for:** documentation-only changes, pure config tweaks, or when user says "skip verification".
**This skill vs github-code-review:** This skill verifies YOUR changes before committing.
`github-code-review` reviews OTHER people's PRs on GitHub with inline comments.
## Step 1 — Get the diff
```bash
git diff --cached
```
If empty, try `git diff` then `git diff HEAD~1 HEAD`.
If `git diff --cached` is empty but `git diff` shows changes, tell the user to
`git add <files>` first. If still empty, run `git status` — nothing to verify.
If the diff exceeds 15,000 characters, split by file:
```bash
…
The line at the top of this page pins the label v2.0.0, 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_rzmbg4wtkkoywxmy
GET https://markdownregistry.com/api/v1/resolve?ref=mateaix/mateclaw/requesting-code-review
GET https://markdownregistry.com/api/v1/blob/bdfa7d4edc1769b1005e5aab3399a15fba083d281398820e8f9eeaa6d15d4ffc
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.
obra/superpowers · skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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
jamditis/claude-skills-journalism · superjawn/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
ibrahim-3d/orchestrator-supaconductor · skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
