Agent skill · Coding
code-review Grade A
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
When it triggers
Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to
Triggering is decided by the description field in the skill’s frontmatter — the agent matches your request against it. If your request never mentions that vocabulary, the skill will not load.
What it does
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
Where it comes from
code-review is published by Matt Pocock in mattpocock/skills, and the source file is mattpocock/skills/blob/main/skills/engineering/code-review/SKILL.md. CSkillBox indexes the frontmatter as written; we do not rewrite the author’s description or claim to have tested the skill.
Security scan
Grade A 100/100 — static scan of this SKILL.md, 2026-11-17.
No risky patterns found in the text: no piped shell downloads, recursive deletes, eval, credential reads or permission bypasses.
A static text scan, not a runtime audit — open the file before you run it. How grades work →
Install
npx skills add mattpocock/skills --skill code-reviewThis copies the skill into your agent’s skills folder. To target one agent explicitly, add -a claude-code (or your agent) to the command. Full install guide →
Before you install
A skill is instructions plus, often, scripts the agent will run. Read the SKILL.md first: check what it executes, which domains it calls, and whether it asks for permissions you are not comfortable granting. A directory entry is not an endorsement.
Community notes
Found a broken install? Know a skill we missed?
One line is enough: the skill name, what happened, and the command you ran. We read every note and fix the index.