Issue Label
- 109 installs
- 11.3k repo stars
- Updated August 5, 2026
- toss/es-toolkit
Issue Label is a maintainer skill that analyzes es-toolkit GitHub issues and applies the appropriate label so the backlog stays consistently triaged.
About
Issue Label is a lightweight es-toolkit maintainer skill that reads a GitHub issue and assigns the correct p0–p3 or discussion label when none are set. It uses title and body cues for bugs, features, docs, TypeScript types, and questions. Maintainers invoke it to keep triage consistent without memorizing the full label table. If the issue already has labels, it reports them and stops.
- Fetches issue title and body with gh issue view
- Skips if labels already exist
- Maps bugs, features, docs, types, and discussions to es-toolkit labels
- Reports applied label with a short justification
Issue Label by the numbers
- 109 all-time installs (skills.sh)
- +4 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #218 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/toss/es-toolkit --skill issue-labelAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 109 |
|---|---|
| repo stars | ★ 11.3k |
| Last updated | August 5, 2026 |
| Repository | toss/es-toolkit ↗ |
How do you quickly classify an unlabeled es-toolkit issue with the right priority and type label?
Analyzes an unlabeled es-toolkit GitHub issue and applies the matching priority/type label via gh.
Who is it for?
es-toolkit maintainers using gh CLI who want fast, consistent issue labeling.
Skip if: Deep PR code review or repositories outside toss/es-toolkit label conventions.
When should I use this skill?
The user runs /issue-label with an issue number or asks to label an unlabeled es-toolkit issue.
What you get
A GitHub label applied via gh issue edit plus a short report explaining the choice.
Files
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,labelsIf 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}Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What if the issue already has labels?
The skill reports existing labels and does not add new ones.
How are major vs minor bugs distinguished?
p0 covers core breakage or crashes; p1 covers edge cases, non-critical bugs, or type errors.
Which tool permissions are needed?
Bash access to gh for viewing and editing issues on toss/es-toolkit.