Issue Label
Productivityissue-labelIssue Label is an Agent Skill for productivity published in the toss/es-toolkit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Suggest and apply GitHub labels to unlabeled issues
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/toss/es-toolkit/blob/HEAD/.claude/skills/issue-label/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-label, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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}