Skip to content
Skill

Code 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 docu

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
326K
Last commit
today
License
MIT
Listing updated
today

When your agent uses it

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".

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 2 files (7 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/code-review to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/code-review &&
cp -R "$tmp/skills/engineering/code-review" ~/.claude/skills/code-review &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/code-review inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/code-review to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/code-review &&
cp -R "$tmp/skills/engineering/code-review" ~/.agents/skills/code-review &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/code-review inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/code-review to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/code-review &&
cp -R "$tmp/skills/engineering/code-review" ~/.cursor/skills/code-review &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/code-review inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/mattpocock/skills.git --path skills/engineering/code-review

Or copy the folder to ~/.gemini/skills/code-review yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/code-review:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/code-review &&
cp -R "$tmp/skills/engineering/code-review" ~/.copilot/skills/code-review &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/code-review inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/mattpocock/skills.git

Then copy skills/skills/engineering/code-review into your agent's skills folder as code-review. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Code review FAQ

How do I install Code review in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/code-review to use it in all your projects, or to .claude/skills/code-review in one project.

Does Code review run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Code review?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Code review?

The closest alternatives to Code review are Rea changelog update, Code review, Acreadiness assess, ML engineering and Code review.

More from mattpocock/skills

  1. Ask which skill or flow fits your situation

    • Open source
    • 326K GitHub stars
  2. Shared vocabulary for designing deep modules

    • Open source
    • 326K GitHub stars
    • Design and media
  3. Diagnosis loop for hard bugs and performance regressions

    • Open source
    • 326K GitHub stars
  4. Build and sharpen a project's domain model

    • Open source
    • 326K GitHub stars
  5. A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    • Open source
    • 326K GitHub stars
  6. Implement a piece of work based on a spec or set of tickets.

    • Open source
    • 326K GitHub stars

Alternatives to Code review

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review pull requests for repository fit, meaningful value, trustworthy provenance, differentiation, and maintainability in awesome-copilot.

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  3. Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  4. Field-tested methodology and concrete recipes for training and operating large-scale LLM/VLM/multi-modal models end to end - choosing and be

    • Open source
    • 19.7K GitHub stars
    • Developer tools
  5. Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, s

    • Open source
    • 3.2K GitHub stars
    • Developer tools