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