Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
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.
The issue tracker should have been provided to you — run `/setup-matt-pocock-skills` if `docs/agents/issue-tracker.md` is missing.
## 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:20260912.84c6c93, 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_6riuwasztcsc563m
GET https://markdownregistry.com/api/v1/resolve?ref=ethanyoq/skill-hub/code-review
GET https://markdownregistry.com/api/v1/blob/9cf46653dd9c710ea1e6c22423caf31a794c88773bc94bdaa23140277f470442
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.
ethanyoq/skill-hub · archives/user-installed-skills/aact-bulk-trials/e07736f27453c7b6/aact-bulk-trials/SKILL.md · 使用 AACT (Aggregate Analysis of ClinicalTrials.gov) PostgreSQL 数据仓库进行批量、历史、聚合性临床试验数据挖掘。Use this skill when the user…
ethanyoq/skill-hub · archives/user-installed-skills/adaptive-quality-gate/b5189ce6c1bdba9b/adaptive-quality-gate/SKILL.md · Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment…
ethanyoq/skill-hub · archives/user-installed-skills/add-changeset/eca9273317fbdf81/add-changeset/SKILL.md · Create a changeset file in .changeset/ that describes a user-facing change for the release notes
ethanyoq/skill-hub · archives/user-installed-skills/add-competitor/72939df8cfcf87bc/add-competitor/SKILL.md · Add a new competitor to the AI Visibility Tool Directory — researches the tool, generates data, takes a screenshot, and…
ethanyoq/skill-hub · archives/user-installed-skills/add-lang/00700e7d79525f4e/add-lang/SKILL.md · Add tree-sitter language support to codegraph end-to-end — wire the grammar + extractor, write tests, then benchmark…
ethanyoq/skill-hub · archives/user-installed-skills/aesthetic/a4c80565d9241341/aesthetic/SKILL.md · Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing…
ethanyoq/skill-hub · archives/user-installed-skills/agent-eval/61ca5bbbd5c736b7/agent-eval/SKILL.md · Benchmark CodeGraph retrieval quality on a real codebase by comparing agent behavior with vs without CodeGraph. Use…
ethanyoq/skill-hub · archives/user-installed-skills/agent-reach/330e35da8cf10b5e/agent-reach/SKILL.md · MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X…
ethanyoq/skill-hub · archives/user-installed-skills/agent-reach/81c9cf0fc08ce044/agent-reach/SKILL.md · MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X…
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…
