Pr Triage

Name: Pr Triage
Author: toss

toss/es-toolkit

110 installs
11.3k repo stars
Updated August 5, 2026
toss/es-toolkit

pr-triage is a Claude agent skill that classifies and summarizes es-toolkit pull requests so developers can focus review time on the highest-risk change areas.

About

pr-triage is a Claude skill bundled with toss/es-toolkit that classifies pull requests by changed paths, runs fast label-specific tests and type checks, and prints a structured triage report for reviewers. Reach for it when you are reviewing es-toolkit PRs and want lodash-compat, new-function checklist, or docs-language checks without manually scanning every file. It expects a PR number argument and uses GitHub CLI against the toss/es-toolkit repository.

Labels PRs via changed-path patterns (compat, core, docs, types, perf)
Runs label-specific vitest and tsc quick checks
Uses gh pr view against toss/es-toolkit
Outputs classification, file groups, and review suggestions

Pr Triage by the numbers

110 all-time installs (skills.sh)
+4 installs in the week ending Jul 27, 2026 (Skillselion tracking)
Ranked #437 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/toss/es-toolkit --skill pr-triage

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/toss/es-toolkit/pr-triage.svg)](https://skillselion.com/skills/toss/es-toolkit/pr-triage)

Installs	110
repo stars	★ 11.3k
Last updated	August 5, 2026
Repository	toss/es-toolkit ↗

How do you quickly know what kind of es-toolkit PR you are reviewing and which tests or doc checks to run first?

Fetches a toss/es-toolkit PR via gh, labels changes (compat, core, docs, types), runs targeted vitest/tsc checks, and outputs a review-focused triage report.

Who is it for?

Maintainers and contributors reviewing numbered pull requests in the toss/es-toolkit repository with gh and yarn available.

Skip if: Repositories other than toss/es-toolkit or reviews that need deep adversarial analysis without the es-toolkit path taxonomy.

When should I use this skill?

You have a PR number and want classification labels, grouped files, and quick vitest or tsc checks before a full review.

What you get

A markdown triage report with labels, changed-file groups, quick-check status, and label-specific review suggestions.

Files

SKILL.mdMarkdownGitHub ↗

PR Triage

Classify and summarize a PR for review.

Input

$ARGUMENTS — PR number (e.g. 1234)

Workflow

1. Fetch PR info

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}