pr-triage · toss — Claude Code skill: what it does, how to install
pr-triage retrieves pull request metadata via GitHub CLI, tags file changes by category, and generates targeted review checklists.
MIT 207 installs ★ 11,397 updated 2026-10-24
npx skills add toss/es-toolkit --skill pr-triage -a claude-codeWhat pr-triage does
This skill inspects a pull request by number. It calls gh pr view to fetch the title, description, author, labels, and file list. Changed paths are mapped to labels such as compat-fix, new-function, core-change, types, or docs.
The workflow uses Bash, Read, Grep, and Glob. Depending on the detected labels, the agent triggers quick checks like yarn vitest run for specific specs or tsc --noEmit for type validation. The resulting report organizes files into groups, checks off build tasks, and highlights what reviewers should look for.
The triage workflow references the toss/es-toolkit repository inside its gh command. Running it without the GitHub CLI binary configured in the terminal will halt execution.
What it helps with
- categorize changed files in a pull request
- generate review suggestions and checklists
- run focused vitest checks on modified functions
- verify TypeScript types without generating output
Example prompts for the agent
- Triage PR 1234 and prepare the review checklist
- Analyze PR 567 with pr-triage
- Run triage on pull request 890
How to install pr-triage
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-triage -a claude-code2Manually: put the files in place
~/.claude/skills/pr-triage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-triage/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-triage -a codex2Manually: put the files in place
.agents/skills/pr-triage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-triage -a cursor2Manually: put the files in place
.cursor/skills/pr-triage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install toss/es-toolkit .claude/skills/pr-triage2Manually: put the files in place
.github/skills/pr-triage/SKILL.md1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-triage -a gemini-cli2Platform CLI
gemini skills install https://github.com/toss/es-toolkit --path .claude/skills/pr-triageManually: put the files in place
.devin/skills/pr-triage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill pr-triage -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-triage
How to install pr-triage in Claude Code?
Run npx skills add toss/es-toolkit --skill pr-triage -a claude-code in your terminal.
Which tools does pr-triage use?
The skill relies on Bash, Read, Grep, and Glob to inspect code and execute terminal commands.
What checks does pr-triage execute during review?
It fetches metadata with gh pr view, then triggers yarn vitest run on affected test suites or tsc --noEmit based on the file labels.
Source text
SKILL.md · MIT
---
name: pr-triage
description: Classify and summarize a PR for efficient review
argument-hint: '<PR number>'
allowed-tools: Bash, Read, Grep, Glob
---
# PR Triage
Classify and summarize a PR for review.
## Input
$ARGUMENTS — PR number (e.g. `1234`)
## Workflow
### 1. Fetch PR info
```bash
gh pr view {number} --repo toss/es-toolkit --json title,body,author,files,labels
```
### 2. Classify the PR
Based on changed files, assign one or more labels:
| Pattern | Label | Review Focus |
| -------------------------------- | ---------------- | --------------------------------------------------------------------- |
| `src/compat/**/*.ts` (not spec) | **compat-fix** | Real lodash inconsistency? Use `/compat-review` to verify. |
| `src/{category}/*.ts` (new file) | **new-function** | Follows design principles? Checklist: impl + spec + re-export + docs. |
| `src/{category}/*.ts` (modified) | **core-change** | Intentional behavior change? Breaking changes? |
| `src/**/*.spec.ts` | **test** | Edge cases covered? |
| `docs/**/*.md` | **docs** | All 4 languages updated? Translation quality? |
| Type-only changes in `.ts` | **types** | Backward-compatible? |
| `benchmarks/**` | **perf** | Fair benchmark? Sound methodology? |
| `.github/**`, config files | **infra** | CI/build impact? |
### 3. Run quick checks per label
- **compat-fix**: `yarn vitest run src/compat/{category}/{fn}.spec.ts`
- **new-function**: Check all checklist items exist (impl, spec, re-export, 4 language docs)
- **core-change**: `yarn vitest run src/{category}/{fn}.spec.ts` + `tsc --noEmit`
- **docs**: Check all 4 language files present and consistent
- **types**: `tsc --noEmit`
### 4. Report
```
## PR #{number} — {title}
### Classification: {labels}
### Changed Files
- {file list grouped by label}
### Quick Checks
- [ ] Tests pass
- [ ] Types pass
- [ ] {label-specific checks}
### Review Suggestions
{What to focus on based on the classification}
```
© toss · MIT · toss/es-toolkit
Similar skills
All skills for Code review and refactoring →pr-triage by other authors comes first.