OpenParable
Skip to content
← Back to skills

PR Triage

Productivity
pr-triage

PR Triage is an Agent Skill for productivity published in the toss/es-toolkit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Classify and summarize a PR for efficient review

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/toss/es-toolkit/blob/HEAD/.claude/skills/pr-triage/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pr-triage, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

PatternLabelReview Focus
src/compat/**/*.ts (not spec)compat-fixReal lodash inconsistency? Use /compat-review to verify.
src/{category}/*.ts (new file)new-functionFollows design principles? Checklist: impl + spec + re-export + docs.
src/{category}/*.ts (modified)core-changeIntentional behavior change? Breaking changes?
src/**/*.spec.tstestEdge cases covered?
docs/**/*.mddocsAll 4 languages updated? Translation quality?
Type-only changes in .tstypesBackward-compatible?
benchmarks/**perfFair benchmark? Sound methodology?
.github/**, config filesinfraCI/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}