New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review PR

by bitovi in bitovi/ai-enablement-prompts

Review all commits on the current branch against remote main before opening a PR.

MITAuto-check: notesDevelopment

Install Review PR

skills CLI
$ npx skills add bitovi/ai-enablement-prompts --skill review-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitovi/ai-enablement-prompts review-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/implement-workflow/skills/review-pr .claude/skills/review-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-pr
GitHub stars
121
Token cost
~1.3k tokens
SKILL.md length
670 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Review all commits on the current branch against remote main before opening a PR.

  • Works in 4 steps: Gather Branch Information → Read the Full Diff → Analyse for Issues → …
  • About to open a PR and wanting a code review first
  • SKILL.md covers Step 1 — Gather Branch…, Step 2 — Read the Full Diff, Step 3 — Analyse for Issues and Step 4 — Output Your Findings, plus 1 more section
  • Calls git

What it does

Review PR is an agent skill from bitovi/ai-enablement-prompts. Review all commits on the current branch against remote main before opening a PR. Surfaces bad code, bad practices, inconsistencies, and files that should not be committed. Use when about to open a PR and wanting a code review first.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Code review. The repository describes itself as: Prompts Bitovi uses for software development. The licence is MIT.

When your agent uses it

  • About to open a PR and wanting a code review first
  • Tasks that involve Pull requests
  • Tasks that involve Code review

Example prompts

  • “/review-pr”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git fetch *), Bash(git log *), Bash(git diff *), Bash(git rev-parse *), Bash(git status *), Read, Glob, Grep

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Gather Branch Information
  2. Read the Full Diff
  3. Analyse for Issues
  4. Output Your Findings

What it can do on your machine

Read from SKILL.md and the folder at commit df229b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git fetch *)
    • Bash(git log *)
    • Bash(git diff *)
    • Bash(git rev-parse *)
    • Bash(git status *)
    • Read
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review PR loads about 1.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 670 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:52
    - `.env`, `.env.*`, `*.pem`, `*.key`, `*.p12`, `*.pfx`, any file containing secrets or credentials

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitovi/ai-enablement-prompts at commit df229b1, republished under its MIT licence (© bitovi). 670 words, ~1,320 tokens.

Download SKILL.mdSave it as .claude/skills/review-pr/SKILL.md (or your agent's skills folder).
name
review-pr
description
Review all commits on the current branch against remote main before opening a PR. Surfaces bad code, bad practices, inconsistencies, and files that should not be committed. Use when about to open a PR and wanting a code review first.
allowed-tools
Bash(git fetch *), Bash(git log *), Bash(git diff *), Bash(git rev-parse *), Bash(git status *), Read, Glob, Grep
disable-model-invocation
true
context
fork
agent
general-purpose

PR Review — Pre-Merge Code Check

You are performing a pre-merge code review of the current branch against remote main (origin/main). Your job is to find real problems and report them concisely. Do not invent findings.

This is the standalone, user-invocable form of the review process. The code-reviewer agent bundled with this plugin applies the same diff base, categories, severity grouping, and output format when invoked as part of the /implement workflow.

Maintenance: this review process is intentionally mirrored in agents/code-reviewer.md so that agent stays self-contained. Keep the two in sync when editing either.

Step 1 — Gather Branch Information

Run these commands to establish the diff base:

git fetch origin
git rev-parse --abbrev-ref HEAD
git log --oneline origin/main..HEAD

This gives you the current branch name and every commit that is not yet in origin/main — exactly what would land on main if this PR merged. (If your project's trunk branch isn't main, substitute it.)

Step 2 — Read the Full Diff

Get the full picture of what changed:

git diff origin/main...HEAD --stat
git diff origin/main...HEAD

Then read every changed file in full using the Read tool. The diff gives you lines; the full file gives you context. You need both.

Step 3 — Analyse for Issues

Work through the categories below. For each, flag only things you have actually seen in the changed files — not speculation.

A. Files that should not be committed
  • .env, .env.*, *.pem, *.key, *.p12, *.pfx, any file containing secrets or credentials
  • node_modules/, dist/, build/, .next/ — compiled or installed artifacts that belong in .gitignore
  • Large binary files with no clear reason to be in version control
  • OS/IDE noise: .DS_Store, Thumbs.db, .vscode/settings.json (unless intentionally shared), .idea/
B. Bad code
  • console.log, console.error, console.warn left in non-test production code
  • TODO, FIXME, HACK, XXX comments left in
  • Commented-out code blocks
  • any (or equivalent) type used as an escape hatch — not as a deliberate, justified typing
  • Magic numbers or hardcoded strings that should be constants or config
  • Functions over ~80 lines; deeply nested conditionals (3+ levels)
C. Bad practices
  • Configuration or secrets read directly from the environment instead of going through the project's settings/config layer
  • Missing auth/permission guard on a new API route or other protected boundary
  • Swallowed errors: empty catch blocks, or catches that only log and silently continue
  • Missing input validation at a new API route boundary
  • Frontend: reading environment config directly in a component instead of the project's config module
  • Frontend: inline styling where a reusable shared class/component already exists
  • Frontend: relative imports where the project uses configured path aliases
Show full SKILL.md (271 more words)Show less
D. Inconsistencies
  • A new route or service that skips a layer of the project's architecture
  • Mixed or inconsistent error-handling style compared to sibling files in the same module
  • A new helper function that duplicates something already in a shared utils module
  • A type/interface defined inline where it belongs in a shared types location

Step 4 — Output Your Findings

Write directly as rendered markdown in the conversation. Do not create any files.

The very first thing in your output must be the Executive Summary. Everything else follows after.

Executive Summary

One short paragraph (3–5 sentences). State:

  • Whether this branch is ready to open a PR or needs changes first
  • The total number of findings and the highest severity reached
  • The single most important thing to address, if anything

Then the detail sections below, in this exact order:

Files That Should Not Be Committed

If none: None found.

One line per file: path/to/file — reason it should not be here

Bad Code

If none: None found.

Group by severity (High / Medium / Low). One line per finding: path/to/file.ts:line — description

Bad Practices

If none: None found.

Group by severity (High / Medium / Low). One line per finding: path/to/file.ts:line — description

Inconsistencies

If none: None found.

Group by severity (High / Medium / Low). One line per finding: path/to/file.ts:line — description

Constraints

  • Do NOT run git commit, git push, or open a PR.
  • Do NOT fix anything — report only.
  • Do NOT report findings that aren't in the diff. If you didn't see it in a changed file, don't mention it.
  • One line per finding. The user can read the code.
  • Never omit a section — if there's nothing to report, write None found.

© bitovi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/implement-workflow/skills/review-pr of bitovi/ai-enablement-prompts.

Open the folder on GitHubat commit df229b1

Compare with similar skills

Review PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review PR this skillbitovi/ai-enablement-prompts121—~1.3kAutomated safety check: NotesMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
Open Code Review CLIalibaba/open-code-review46k—~3.1kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
Understand Diff AnalysisEgonex-AI/Understand-Anything86k—~1.4kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    46k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Review

    flutter/flutter

    Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.

    179k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from bitovi/ai-enablement-prompts

All 40 skills in this repo

  • Component Registry

    bitovi/ai-enablement-prompts

    Track reusable UI components and unextracted patterns. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~597 tokensUpdated 29 days ago
    Auto-check passed

  • Computed Styles

    bitovi/ai-enablement-prompts

    Extract and compare computed CSS styles between a baseline URL and a dev/Storybook URL using Playwright MCP evaluate calls.

    121 GitHub stars~2.4k tokensUpdated 29 days ago
    Auto-check passed

  • Create Plugin

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a plugin", "add a plugin", "make a new plugin", "build a plugin", or wants to package skills into an installable plugin for this marketplace.

    121 GitHub stars~2k tokensUpdated 29 days ago
    Auto-check passed

  • Create React Modlet

    bitovi/ai-enablement-prompts

    Create React components, hooks, or utilities following the modlet pattern.

    121 GitHub stars~2.1k tokensUpdated 29 days ago
    Auto-check passed

  • Create Skill

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a skill", "add a skill", "make a new skill", "build a skill", or wants to automate a repeated workflow into a reusable prompt.

    121 GitHub stars~1.6k tokensUpdated 29 days ago
    Auto-check passed

  • Create Skill

    bitovi/ai-enablement-prompts

    Create new Agent Skills for this project. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~1.7k tokensUpdated 29 days ago
    Auto-check passed

Categories

Questions about Review PR

What does Review PR do?

Review all commits on the current branch against remote main before opening a PR. Review PR is an agent skill from bitovi/ai-enablement-prompts. Review all commits on the current branch against remote main before opening a PR.

When should I use Review PR?

Review PR fits situations like: about to open a PR and wanting a code review first; tasks that involve Pull requests; tasks that involve Code review.

How do I install Review PR in Claude Code?

Run `npx skills add bitovi/ai-enablement-prompts --skill review-pr -a claude-code`. Or copy the skill folder (plugins/implement-workflow/skills/review-pr in bitovi/ai-enablement-prompts) into .claude/skills/review-pr in your project. Claude Code loads it when a task matches its description.

How do I install Review PR in Codex?

Run `npx skills add bitovi/ai-enablement-prompts --skill review-pr -a codex`. Or copy the skill folder (plugins/implement-workflow/skills/review-pr in bitovi/ai-enablement-prompts) into .agents/skills/review-pr in your project. Codex loads it when a task matches its description.

Can I use Review PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitovi/ai-enablement-prompts --skill review-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr, .gemini/skills/review-pr, .github/skills/review-pr and .opencode/skills/review-pr in your project.

What does Review PR need to run?

Going by SKILL.md and its folder, Review PR needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash(git fetch *), Bash(git log *), Bash(git diff *), Bash(git rev-parse *), Bash(git status *), Read, Glob, Grep.

Does Review PR access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review PR safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Review PR use?

Review PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review PR use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review PR?

Skills that share tags, products or a category with Review PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and GitHub Review Iteration (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review PR?

bitovi (a GitHub organization) maintains it in bitovi/ai-enablement-prompts, which has 121 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on September 11, 2026.

Source: bitovi/ai-enablement-prompts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.