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. If `docs/agents/issue-tracker.md` is missing, tell the user to run `/setup-matt-pocock-skills`.
## 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:20260916.5a385b8, 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_sctnqeowzyw4dkjx
GET https://markdownregistry.com/api/v1/resolve?ref=mambo-wang/codewiki-plus/code-review
GET https://markdownregistry.com/api/v1/blob/47f4e52c21694def9c7c11cbfbf891ca35eac7a93e395797515be3c8a409ae50
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.
mambo-wang/codewiki-plus · .codebuddy/skills/blog-writing-specialist/SKILL.md · Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation…
mambo-wang/codewiki-plus · .codebuddy/skills/claude-handoff/SKILL.md · Hand the current conversation off to a fresh background agent that picks up the work immediately.
mambo-wang/codewiki-plus · .codebuddy/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
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…
