Skip to content
Skill

Code review

Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
28.1K
Last commit
9 days ago
License
MIT
Listing updated
today

When your agent uses it

Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.

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 1 file (1 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

This skill ships in the pm-ai-shipping plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add phuryn/pm-skills
/plugin install pm-ai-shipping@pm-skills

Or copy only this skill to ~/.claude/skills/code-review:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/phuryn/pm-skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/code-review &&
cp -R "$tmp/pm-ai-shipping/skills/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/phuryn/pm-skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/code-review &&
cp -R "$tmp/pm-ai-shipping/skills/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/phuryn/pm-skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/code-review &&
cp -R "$tmp/pm-ai-shipping/skills/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/phuryn/pm-skills.git --path pm-ai-shipping/skills/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/phuryn/pm-skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/code-review &&
cp -R "$tmp/pm-ai-shipping/skills/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/phuryn/pm-skills.git

Then copy pm-skills/pm-ai-shipping/skills/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. Or install the pm-ai-shipping plugin, which includes it: /plugin marketplace add phuryn/pm-skills, then /plugin install pm-ai-shipping@pm-skills.

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, Gem devops guidelines, PR screenshots and Make repo contribution.

More from phuryn/pm-skills

  1. Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it

    • Open source
    • 28.1K GitHub stars
  2. Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it

    • Open source
    • 28.1K GitHub stars
  3. Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights

    • Open source
    • 28.1K GitHub stars
  4. Generate SQL queries from natural language descriptions

    • Open source
    • 28.1K GitHub stars
    • Databases
  5. Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results

    • Open source
    • 28.1K GitHub stars
  6. Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market seg

    • Open source
    • 28.1K 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 the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools