Issue Label
Analyze issue content and assign appropriate labels.
Input
$ARGUMENTS — Issue number (e.g. 1234)
Available Labels
| 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 |
Workflow
1. Fetch issue
gh issue view {number} --repo toss/es-toolkit --json title,body,labels
If labels already exist, report them and stop.
2. Analyze content
From title and body, identify:
- Is it a bug report? (error messages, "doesn't work", "incorrect", "doesn't match lodash")
- Is it a feature request? ("add", "implement", "support")
- Is it about docs? ("docs", "typo", "translation", "example")
- Is it about types? ("type", "TypeScript", "generic", "inference")
- Is it a question? (question marks, "how to", "is it possible")
3. Apply label
gh issue edit {number} --repo toss/es-toolkit --add-label "{label}"
4. Report
## Issue #{number} — {title}
### Applied Label: {label}
### Reason: {why this label fits}
1---2name: issue-label3description: Suggest and apply GitHub labels to unlabeled issues4---5
6# Issue Label
7
8Analyze issue content and assign appropriate labels.
9
10## Input
11
12$ARGUMENTS — Issue number (e.g. `1234`)
13
14## Available Labels
15
16| Label | When to use |
17| ---------------------- | ------------------------------------------------------------- |
18| `p0: major bug` | Core function broken, incorrect results, crashes |
19| `p1: minor bug` | Edge case failures, non-critical behavior issues, type errors |
20| `p1: docs bug` | Wrong/outdated documentation, broken links |
21| `p2: optimization` | Performance improvements, bundle size reduction |
22| `p2: new feature` | New function or capability request |
23| `p2: type enhancement` | TypeScript type improvements, better generics |
24| `p2: refactoring` | Code cleanup, internal improvements |
25| `p2: docs enhancement` | New docs, translations, better examples |
26| `p3: discussion` | Questions, design discussions, RFCs |
27| `help wanted` | Good for external contributors |
28
29## Workflow
30
31### 1. Fetch issue
32
33```bash
34gh issue view {number} --repo toss/es-toolkit --json title,body,labels
35```
36
37If labels already exist, report them and stop.
38
39### 2. Analyze content
40
41From title and body, identify:
42
43- Is it a bug report? (error messages, "doesn't work", "incorrect", "doesn't match lodash")
44- Is it a feature request? ("add", "implement", "support")
45- Is it about docs? ("docs", "typo", "translation", "example")
46- Is it about types? ("type", "TypeScript", "generic", "inference")
47- Is it a question? (question marks, "how to", "is it possible")
48
49### 3. Apply label
50
51```bash
52gh issue edit {number} --repo toss/es-toolkit --add-label "{label}"
53```
54
55### 4. Report
56
57```
58## Issue #{number} — {title}
59
60### Applied Label: {label}
61### Reason: {why this label fits}
62```
toss