Menü
Classify and summarize a PR for efficient review
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create a new es-toolkit release (version bump, changelog, tag)
es-toolkit usage guide covering installation, import patterns, and setup for Node.js, Bun, Deno, and browsers. Use when the user asks how to install, import, or set up es-toolkit in their project.
Guide migrating lodash code to es-toolkit. Use when the user wants to migrate from lodash, replace lodash imports, reduce bundle size by switching to es-toolkit, or understand the difference between es-toolkit and es-toolkit/compat.
Analyze code or requirements and recommend the best es-toolkit functions. Use when the user asks which es-toolkit function to use, needs help finding a utility, or wants alternatives to manual implementations.
Verify compat PR claims by running lodash vs es-toolkit/compat at runtime
Suggest and apply GitHub labels to unlabeled issues
| name | pr-triage |
| description | Classify and summarize a PR for efficient review |
| argument-hint | <PR number> |
| allowed-tools | Bash, Read, Grep, Glob |
Classify and summarize a PR for review.
$ARGUMENTS — PR number (e.g. 1234)
gh pr view {number} --repo toss/es-toolkit --json title,body,author,files,labels
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? |
yarn vitest run src/compat/{category}/{fn}.spec.tsyarn vitest run src/{category}/{fn}.spec.ts + tsc --noEmittsc --noEmit## 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}