Skip to main content
skill CX Codex

issue-label — Claude Code skill: what it does, how to install

issue-label is a Claude Code skill that reads GitHub issue content, selects a label from the project matrix, and applies it with one command.

MIT 206 installs ★ 11,397 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add toss/es-toolkit --skill issue-label -a claude-code
Open on GitHub

What issue-label does

Skill takes an issue number, fetches it with gh issue view, analyzes title and body for keywords — "doesn't work", "add", "docs", "type" — and assigns one of ten labels: from p0: major bug to p3: discussion. If labels already exist, it stops and shows the list. Applies the label with gh issue edit and returns a report explaining the choice.

Skill is hardcoded for the toss/es-toolkit repository and its label matrix. For other projects, you'll need to edit the table manually. Requires GitHub CLI (gh) with write access to the repository.

What it helps with

  • triage unlabeled GitHub issues
  • assign priority to bug reports by content
  • distinguish feature requests from questions automatically
  • apply label from project matrix with one command

Example prompts for the agent

  • Label issue 1234 with the appropriate label
  • Analyze issue 567 and apply the right label
  • Assign labels to unlabeled issues from 100 to 150

How to install issue-label

1Skills CLI (Vercel)

npx skills add toss/es-toolkit --skill issue-label -a claude-code

2Manually: put the files in place

~/.claude/skills/issue-label/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/issue-label/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about issue-label

How to install issue-label in Claude Code?

Run npx skills add toss/es-toolkit --skill issue-label -a claude-code, the skill will appear in ~/.claude/skills/issue-label/SKILL.md.

What does issue-label do?

Skill reads a GitHub issue, analyzes its content, and assigns one of ten project labels — from critical bug to discussion.

Can I use issue-label for another repository?

Skill is hardcoded for toss/es-toolkit and its label matrix. For another repository, open SKILL.md and replace the repository name and label table.

Source text

SKILL.md · MIT
---
name: issue-label
description: Suggest and apply GitHub labels to unlabeled issues
argument-hint: '<issue number>'
allowed-tools: Bash, Read, Grep
---

# 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

```bash
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

```bash
gh issue edit {number} --repo toss/es-toolkit --add-label "{label}"
```

### 4. Report

```
## Issue #{number} — {title}

### Applied Label: {label}
### Reason: {why this label fits}
```

© toss · MIT · toss/es-toolkit

Similar skills

All skills for Git and GitHub →

From the same set9

Project sponsors

Companies that keep this analytics open