Suggest and apply GitHub labels to unlabeled issues
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}