pr-review · toss — Claude Code skill: what it does, how to install
pr-review — a skill for deep pull request reviews: reads source code, compares changes, detects breaking changes, and delivers a verdict.
MIT 209 installs ★ 11,397 updated 2026-10-24
npx skills add toss/es-toolkit --skill pr-review -a claude-codeWhat pr-review does
pr-review fetches open PRs from the repository (gh pr list), reads the current code on main and the diff for each PR, then checks whether the function signature breaks, whether behavior aligns with JS spec or lodash conventions, and whether all four language versions of the documentation are updated. For PRs labeled compat-fix it runs /compat-review, for core-change it runs Vitest tests, for types it runs TypeScript checks.
The skill outputs a report per PR: what's changing, what the current code does, checkpoints to verify, and a verdict — merge, request changes, or reject. At the end it groups duplicates by function name and modified files. Requires GitHub CLI; without gh in PATH it will not run.
What it helps with
- read code in the current branch and in the PR diff to understand the actual change
- detect breaking changes and verify JS spec alignment
- run tests and type checks for PRs labeled
core-changeandtypes - find duplicate PRs by modified files
- output a table with verdicts: merge, request changes, or hold for discussion
Example prompts for the agent
- Review the last 10 open PRs in
toss/es-toolkit - Review 20 PRs and show which are ready to merge
- Run
/pr-review 15and find duplicates
How to install pr-review
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-review -a claude-code2Manually: put the files in place
~/.claude/skills/pr-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-review/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-review -a codex2Manually: put the files in place
.agents/skills/pr-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-review -a cursor2Manually: put the files in place
.cursor/skills/pr-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install toss/es-toolkit .claude/skills/pr-review2Manually: put the files in place
.github/skills/pr-review/SKILL.md1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/toss/es-toolkit --path .claude/skills/pr-reviewManually: put the files in place
.devin/skills/pr-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pr-review
How do I install pr-review in Claude Code?
Run npx skills add toss/es-toolkit --skill pr-review -a claude-code, the skill will appear in ~/.claude/skills/pr-review/SKILL.md.
What does pr-review do?
The skill fetches open PRs via GitHub CLI, reads source code and diffs, checks for breaking changes and JS spec alignment, runs tests for core-change and types labels, and delivers a verdict for each PR.
What does pr-review require to work?
GitHub CLI (gh) must be installed and available in PATH. The skill calls gh pr list, yarn vitest, and tsc --noEmit for checks.
Source text
SKILL.md · MIT
---
name: pr-review
description: Review recent PRs with deep context and label-specific checks
argument-hint: '[count=10]'
allowed-tools: Bash, Read, Grep, Glob, Skill
---
# PR Review
Fetch recent PRs, classify, read source code, and produce contextual reviews.
## Input
$ARGUMENTS — Number of PRs (default: `10`)
Examples:
- `/pr-review` — 10 most recent open PRs
- `/pr-review 20` — 20 PRs
## Workflow
### 1. Fetch recent PRs
```bash
gh pr list --repo toss/es-toolkit --state open --limit {count} --json number,title,author,labels,createdAt
```
### 2. Triage each PR
Run `/pr-triage {number}` for each PR to classify.
### 3. Deep review per PR
For each PR, go beyond classification — **read the actual source code** and provide context:
#### a. Read current code
Read the files being modified on main to understand the current behavior:
- Function source: what it does, how it works
- Existing tests: what's already covered
- JSDoc: documented behavior and examples
#### b. Understand the PR change
Read the diff to understand what's changing:
- What's the before vs after?
- Why does the contributor say this change is needed?
- Does the change match what the code actually needs?
#### c. Assess impact
- **Breaking changes**: Does the function signature change? Will existing users be affected?
- **JS spec alignment**: Does current behavior follow JS/lodash conventions? Does the PR break that?
- **Scope**: Are all affected files updated? (e.g., docs in all 4 languages, related functions)
- **Design principles**: Does this align with es-toolkit's 85% use case / simplicity philosophy?
#### d. Label-specific checks
- **compat-fix**: Run `/compat-review {number}`
- **new-function**: Check completeness (impl + spec + re-export + 4 lang docs)
- **core-change**: `yarn vitest run src/{category}/{fn}.spec.ts` + review breaking impact
- **docs**: Check all 4 language files updated consistently
- **types**: `tsc --noEmit`
### 4. Detect duplicates
Group PRs by same function name or same files modified.
### 5. Report per PR
For each PR, output:
```
### PR #{number} — {title}
**Classification**: {labels}
**Changed files**: {summary}
**Current code**: {what the function does now, with code snippet}
**PR change**: {what's changing and why, with before/after}
**Context**: {JS spec, lodash behavior, design principle considerations}
**Checkpoints**:
- {specific things to verify}
**Verdict**: {merge / merge with changes / hold for discussion / reject}
```
### 6. Summary
```
## PR Review — {date}
| # | Title | Label | Verdict |
|---|-------|-------|---------|
- {N} ready to merge
- {N} need changes
- {N} need discussion
- {N} potential duplicates
```
© toss · MIT · toss/es-toolkit
Similar skills
All skills for Code review and refactoring →pr-review by other authors comes first.