Use when reviewing a branch, PR, or WIP since a commit, tag, or merge-base. Two-axis Standards and Spec review via parallel sub-agents.
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
Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
- **Standards**: does the code conform to this repo's documented coding standards?
- **Spec**: does the code faithfully implement the originating issue / spec?
Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.
Read ticket identifiers from the `workflow-profile` skill and `safety-overrides`. Do not close, fix, or resolve tracker items; cite them as `Refs #N`.
## Process
### 1. Pin the fixed point
Whatever the user said is the fixed point (a commit SHA, branch name, tag, `main`, `HEAD~5`, etc.). If they didn't specify one, ask for it.
Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`.
Before going further, confirm the fixed point resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents.
### 2. Identify the spec source
Look for the originating spec, in this order:
…
The line at the top of this page pins the label git:20261006.f349c21, 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_baqkbhyxs2vjsio6
GET https://markdownregistry.com/api/v1/resolve?ref=kunanonj/ai-skills-hub/code-review
GET https://markdownregistry.com/api/v1/blob/6667095930e1faa230c232db8fbb3f3eff19a1fa0dfc9fea8bc7dca2aebdbe23
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.
kunanonj/ai-skills-hub · plugins/superstacks/skills/diagnosing-bugs/SKILL.md · Use when the user says diagnose or debug this, or reports something broken, throwing, failing, or slow.
kunanonj/ai-skills-hub · plugins/superstacks/skills/domain-modeling/SKILL.md · Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
kunanonj/ai-skills-hub · plugins/superstacks/skills/gardening/SKILL.md · Use when finding small maintenance work. One concern per PR, each with a verify command and a small diff budget.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grill-with-docs/SKILL.md · Use when grilling a plan or design that should also produce ADRs and a glossary as you go.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grilling/SKILL.md · Use when the user wants to stress-test a plan, decision, or idea, or uses any grill trigger phrases.
kunanonj/ai-skills-hub · plugins/superstacks/skills/how/SKILL.md · Use for how-does-X-work walkthroughs, placement, ownership, and layering questions before changing code.
kunanonj/ai-skills-hub · plugins/superstacks/skills/intake-triage/SKILL.md · Use when a coordinator has a batch of bug reports, feedback, or alerts. Deduplicate, group, score two-way vs one-way…
kunanonj/ai-skills-hub · plugins/superstacks/skills/interrogate/SKILL.md · Use for interrogate, adversarial review, multi-model review, challenge this, stress test this code, or find blind spots.
kunanonj/ai-skills-hub · plugins/superstacks/skills/mistake-to-constraint/SKILL.md · Use when a mistake repeats. Encode it as the strongest guard — type or runtime, lint, test, directory convention, then…
kunanonj/ai-skills-hub · plugins/superstacks/skills/sample-review/SKILL.md · Use when sampling recently merged PRs against repo standards and CONSTRAINTS.md. Propose environment tightenings, not…
agno-agi/agno · cookbook/02_agents/16_skills/sample_skills/code-review/SKILL.md · Code review assistance with linting, style checking, and best practices
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/team_skills/code-review/SKILL.md · Review Python code for bugs, missing tests and security issues using the team's shared standards
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
nteract/semiotic · .github/skills/code-review/SKILL.md · Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence. Use for GitHub…