mcpField
I
issue-label

issue-label

github.com/tossDevelopment11.4k187 installsUpdated 2d ago
Repository

About issue-label

issue-label is a skill for classifying issues in toss/es-toolkit. It checks an issue’s title, body, and existing labels, then applies an appropriate label and reports the reason.

Key features

  1. 01Fetch issue title, body, and labels
  2. 02Stop and report existing labels
  3. 03Choose labels by issue type
  4. 04Apply a label and explain why

Use cases

  1. 01Assign severity to bug reports
  2. 02Distinguish feature, documentation, and type issues
  3. 03Label questions or discussions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/toss/es-toolkit --skill issue-label

After installing, type/issue-labelin Claude Code to confirm it loaded.

Details

From the project README

Issue Label

Analyze issue content and assign appropriate labels.

Input

$ARGUMENTS — Issue number (e.g. 1234)

Available Labels

LabelWhen to use
p0: major bugCore function broken, incorrect results, crashes
p1: minor bugEdge case failures, non-critical behavior issues, type errors
p1: docs bugWrong/outdated documentation, broken links
p2: optimizationPerformance improvements, bundle size reduction
p2: new featureNew function or capability request
p2: type enhancementTypeScript type improvements, better generics
p2: refactoringCode cleanup, internal improvements
p2: docs enhancementNew docs, translations, better examples
p3: discussionQuestions, design discussions, RFCs
help wantedGood 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}

Comments

Markdown supported