Agent skill · software engineering · aiskillstore
review
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/PRD 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".
Why this skill is useful
Adds a parallel review process for code changes against standards and specifications, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Review 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 / PRD / 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. Don't be opinionated; pass it through. If they didn't specify one, ask: "Review against what — a branch, a commit, or main?" Don't proceed until you have 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. 2. Identify the spec source Look for the originating spec, in this order: 1. Issue references in the commit messages (#123, Closes #45, GitLab !67, etc.) — fetch via the workflow in docs/agents/issue-tracker.md. 2. A path the user passed as an argument. 3. A PRD/spec file under docs/, specs/, or .scratch/ matching the branch name or feature. 4. If nothing is found, ask the user where the spec is. If they say there isn't one, the Spec sub-agent will skip and report "no spec available". 3. Identify the standards sources Anything in the repo that documents how code should be written. Common locations: CLAUDE.md, AGENTS.md CONTRIBUTING.md CONTEXT.md, CONTEXT-MAP.md, per-context CONTEXT.md files docs/adr/ (architectural decisions are standards) .editorconfig, eslint.config., biome.json, prettier.config., tsconfig.json (machine-enforced standards — note them but don't re-check what tooling already checks) Any STYLE.md, STANDARDS.md, STYLEGUIDE.md, or similar at the repo root or under docs/ Collect the list of files. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/review--7e9196