Classify and summarize a PR for efficient review
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
| name | issue-label |
| description | Suggest and apply GitHub labels to unlabeled issues |
| argument-hint | <issue number> |
| allowed-tools | Bash, Read, Grep |
Analyze issue content and assign appropriate labels.
$ARGUMENTS — Issue number (e.g. 1234)
| Label | When to use |
|---|---|
p0: major bug | Core function broken, incorrect results, crashes |
p1: minor bug | Edge case failures, non-critical behavior issues, type errors |
p1: docs bug | Wrong/outdated documentation, broken links |
p2: optimization | Performance improvements, bundle size reduction |
p2: new feature | New function or capability request |
p2: type enhancement | TypeScript type improvements, better generics |
p2: refactoring | Code cleanup, internal improvements |
p2: docs enhancement | New docs, translations, better examples |
p3: discussion | Questions, design discussions, RFCs |
help wanted | Good for external contributors |
gh issue view {number} --repo toss/es-toolkit --json title,body,labels
If labels already exist, report them and stop.
From title and body, identify:
gh issue edit {number} --repo toss/es-toolkit --add-label "{label}"
## Issue #{number} — {title}
### Applied Label: {label}
### Reason: {why this label fits}