PR Review
jaemk/cached
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/cached.
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update.
Install PR Review
$ npx skills add jaemk/self_update --skill pr-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jaemk/self_update pr-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-review .claude/skills/pr-review && rm -rf skills-srcUse ~/.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/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .claude/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jaemk/self_update --skill pr-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jaemk/self_update pr-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pr-review .agents/skills/pr-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .agents/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jaemk/self_update --skill pr-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jaemk/self_update pr-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pr-review .cursor/skills/pr-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .cursor/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jaemk/self_update.git --path .agents/skills/pr-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jaemk/self_update --skill pr-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jaemk/self_update pr-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pr-review .gemini/skills/pr-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .gemini/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jaemk/self_update pr-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jaemk/self_update --skill pr-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pr-review .github/skills/pr-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .github/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jaemk/self_update --skill pr-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jaemk/self_update pr-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaemk/self_update.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pr-review .opencode/skills/pr-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/jaemk/self_update/tree/master/.agents/skills/pr-review into .opencode/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-review- GitHub stars
- 961
- Token cost
- ~1.5k tokens
- SKILL.md length
- 798 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update.
- Works in 4 steps: Acquire the diff → Spawn two independent sub-agents in… → Evaluate all findings → …
- Asked to review this PR
- SKILL.md covers Scope — what this does and…, Model tiers, Input and Steps
- Calls git and gh
What it does
PR Review is an agent skill from jaemk/self_update. Targeted, read-only review of a PR or checked-out branch. Acquires the diff (a PR number, or the current branch vs origin/master), spawns an independent code-review sub-agent and a library-consumer sub-agent in parallel, then aggregates their findings into a single report with severity and a valid / already-fixed / invalid verdict for each. Read-only — it does not edit files, commit, push, or touch the GitHub PR conversation. The review sub-agents default to Sonnet but can be overridden per run (e.g. to opus)…
Its SKILL.md is about 1.5k 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 Subagents, Pull requests and Code review. It works with GitHub and Rust. The repository describes itself as: Self updates for rust executables. The licence is MIT.
When your agent uses it
- Asked to review this PR
- Review the branch
- Whats wrong with this diff
- Do a code review
Example prompts
- “review this PR”
- “review the branch”
- “s wrong with this diff”
- “/pr-review”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Agent
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fc84045. 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:
BashReadAgent
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
PR Review loads about 1.5k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 798 words of instructions outside code blocks.
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.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Agent
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 jaemk/self_update at commit fc84045, republished under its MIT licence (© jaemk). 798 words, ~1,544 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-review/SKILL.md (or your agent's skills folder).- name
- pr-review
- description
- Targeted, read-only review of a PR or checked-out branch. Acquires the diff (a PR number, or the current branch vs origin/master), spawns an independent code-review sub-agent and a library-consumer sub-agent in parallel, then aggregates their findings into a single report with severity and a valid / already-fixed / invalid verdict for each. Read-only — it does not edit files, commit, push, or touch the GitHub PR conversation. The review sub-agents default to Sonnet but can be overridden per run (e.g. to opus). Use when asked to "review this PR", "review the branch", "what's wrong with this diff", "do a code review", or "review with opus". For the full review → fix → push → resolve loop, use `pr-cycle` (which delegates its review step here).
- allowed-tools
- Bash, Read, Agent
PR Review
Produce a fresh, read-only review of a PR or a checked-out branch and report the
findings. This is the "review" half of the PR workflow, extracted so it can be run
on its own. The orchestrator skill pr-cycle calls this skill to obtain its local
findings, then goes on to address, push, and resolve them.
Scope — what this does and does not do
Does: acquire the diff, spawn the two read-only review sub-agents, evaluate their findings, and report them with severity and a verdict.
Does NOT: edit files, run the CI checks, regenerate the README, commit, or push;
and it does not interact with the GitHub PR conversation — it does not read
existing PR comments/threads, resolve or minimize them, edit the PR body, or
re-request Copilot review. Those belong to pr-cycle. This skill only generates a
fresh agent-based review of the code itself.
This skill is purely advisory: its output is a findings report for a human (or for
pr-cycle) to act on. It applies no changes.
Model tiers
| Tier | What | Step | Model |
|---|---|---|---|
| 1 — cheap delegation | Read-only review sub-agents | 2 | Sonnet (pinned in agent def; overridable per-run, e.g. to opus — see Input) |
| 2 — judgment core | Classify findings into valid / already-fixed / invalid | 3, 4 | session model (use Opus for the verdict pass) |
Input
A target and an optional review-agent model override, in any order.
- Target: either a PR number, or nothing (review the current checked-out
branch). If a PR number is omitted you may infer one from the current branch with
gh pr view --json number(run with the sandbox disabled — GitHub needs network), but a PR is not required: a plain checked-out branch is reviewed by diffing againstorigin/master. - Review-agent model: the model used by the two sub-agents (
pr-code-reviewer,pr-consumer-reviewer) defaults tosonnet, but can be overridden. If the input names a model (e.g. "review with opus", "opus reviewers", "model=opus"), pass that model to the Agent tool'smodelparameter when spawning both sub-agents in step 2. With no override, omitmodelso each agent uses its pinned Sonnet default.
Announce the resolved target and review-agent model at the start — e.g. "Reviewing the current branch with opus reviewers" or "Reviewing PR #181 with Sonnet reviewers" — before spawning anything.
Steps
1. Acquire the diff
The diff is git diff origin/master, which works for any checked-out branch whether
or not it has a PR:
git diff origin/masterIf you are targeting a specific PR, the pr-cycle helper prints the identical diff
and is equivalent:
.agents/skills/pr-cycle/pr.py PR_NUMBER diffCapture the full diff text — it is fed verbatim to both sub-agents.
Show full SKILL.md (376 more words)Show less
2. Spawn two independent sub-agents in parallel
Agent A — code reviewer: Spawn with the pr-code-reviewer agent type. Prompt must
include:
- The PR number (or branch name, if there is no PR)
- The full diff (from step 1)
Agent B — library consumer: Spawn with the pr-consumer-reviewer agent type. Prompt
must include:
- The PR number (or branch name)
- The full diff
- The current
src/lib.rsdoc comments andREADME.md(or relevant excerpts covering the changed APIs)
Both agents are read-only (no Edit/Write tools) and carry their full rubrics in their agent definitions — do not re-specify the rubric in the prompt.
Model override: if the input requested a review-agent model (see Input),
pass it to the Agent tool's model parameter on both spawns (e.g. model: "opus").
With no override, omit model so each agent uses its pinned Sonnet default.
Launch both agents in parallel. Wait for both to complete before proceeding.
3. Evaluate all findings
Collect both sub-agent reports. For each finding, assign a verdict and explain your reasoning:
- Valid — the concern is real and the code should change.
- Already fixed — the concern was valid in principle but the current code already handles it (the reviewer was working from a partial view).
- Invalid — the finding is incorrect or environment-specific (e.g. a rustc-version diagnostic difference, or a "missing" feature gate that is actually present).
This verdict pass is the judgment core; run it on the session model (use Opus). Do not
soften or pad — an invalid finding called valid sends pr-cycle (or a human) chasing a
non-issue.
4. Report
Present a single consolidated report:
- The target reviewed (PR number or branch name) and the review-agent model used.
- Code-reviewer findings: total count, broken down by severity (high / medium / low), and by verdict (valid / already-fixed / invalid).
- Consumer-reviewer findings: the same breakdown.
- For each valid finding: a one-line summary, the
file:line(or area), and why it matters — enough thatpr-cycleor a human can act on it without re-reading the agent output. - For each invalid or already-fixed finding: a one-line note on why it was ruled so.
- A closing one-line verdict: is the branch/PR clean, or are there valid findings to address (and how many high/medium)?
Do not apply any fix. If the caller wants the findings addressed and pushed, that is
pr-cycle's job.
© jaemk, 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 .agents/skills/pr-review of jaemk/self_update.
Open the folder on GitHubat commit fc84045
Compare with similar skills
PR Review 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Review this skilljaemk/self_update | 961 | — | ~1.5k | Automated safety check: Notes | MIT | |
| PR Reviewjaemk/cached | 2.1k | — | ~2.5k | Automated safety check: Notes | MIT | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Cherry Studio PR ReviewCherryHQ/cherry-studio | 53k | — | ~3.9k | Automated safety check: Pass | AGPL-3.0 | |
| PR Cyclejaemk/cached | 2.1k | — | ~4.8k | Automated safety check: Notes | MIT | |
| Firewood Reviewava-labs/firewood | 153 | — | ~2.1k | Automated safety check: Notes | Custom licence |
Similar skills
- Official
GitHub Review Iteration
prisma/orm
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.
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
PR Cycle
jaemk/cached
PR review-and-update cycle — the orchestrator that takes a PR from review to resolved.
Firewood Review
ava-labs/firewood
A skill your agent uses when reviewing ava-labs/firewood code changes — pull request or local workspace.
Pull Request Code Review Orchestrator
openinterpreter/openinterpreter
Run a final code review on a pull request
More from jaemk/self_update
Release
jaemk/self_update
Prepare a release (bump the crate version, update CHANGELOG.md with a migration guide for breaking changes, regenerate README, commit), or run a pre-release review.
Related
Categories
Questions about PR Review
What does PR Review do?
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update. PR Review is an agent skill from jaemk/self_update. Targeted, read-only review of a PR or checked-out branch.
When should I use PR Review?
PR Review fits situations like: asked to review this PR; review the branch; whats wrong with this diff; do a code review.
How do I install PR Review in Claude Code?
Run `npx skills add jaemk/self_update --skill pr-review -a claude-code`. Or copy the skill folder (.agents/skills/pr-review in jaemk/self_update) into .claude/skills/pr-review in your project. Claude Code loads it when a task matches its description.
How do I install PR Review in Codex?
Run `npx skills add jaemk/self_update --skill pr-review -a codex`. Or copy the skill folder (.agents/skills/pr-review in jaemk/self_update) into .agents/skills/pr-review in your project. Codex loads it when a task matches its description.
Can I use PR Review 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 jaemk/self_update --skill pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-review, .gemini/skills/pr-review, .github/skills/pr-review and .opencode/skills/pr-review in your project.
What does PR Review need to run?
Going by SKILL.md and its folder, PR Review needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash, Read, Agent.
Does PR Review access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Review safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does PR Review use?
PR Review 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 PR Review use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 PR Review?
Skills that share tags, products or a category with PR Review: PR Review (jaemk/cached, 2.1k stars), GitHub Review Iteration (prisma/orm, 48k stars), Cherry Studio PR Review (CherryHQ/cherry-studio, 53k stars) and PR Cycle (jaemk/cached, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Review?
jaemk (a GitHub user) maintains it in jaemk/self_update, which has 961 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 2, 2026.
Source: jaemk/self_update on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.