Skip to content
Back to skills

Label Issue

ASecurity

Add relevant labels to a GitHub issue based on its description, and recommend new labels if needed.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
toolsgogit

Works with

  • cli

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add tomzx/agents --skill label-issue --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Label Issue?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Label Issue
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomzx-label-issue/badge)](https://www.skillsdirectory.com/skills/tomzx-label-issue)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: label-issue
description: Add relevant labels to a GitHub issue based on its description, and recommend new labels if needed.
argument-hint: "<issue-number>"
---

# Label GitHub Issue

Reads a GitHub issue and applies appropriate existing labels based on its content, then recommends new labels if the current set is insufficient.

## Prerequisites

- `gh` CLI authenticated with triage or write access to the repository
- Issue number (`$1`) referencing an existing issue in the current repository context

## Workflow

```
Fetch issue details ($1)
        |
        v
Fetch available labels
        |
        v
Match issue content to labels
        |
        v
Matching labels found?
   /         \
 Yes           No
  |             |
  v             v
Apply labels  Skip label
via gh        add step
  |             |
  +------+------+
         |
         v
New labels needed?
   /         \
 Yes           No
  |             |
  v             v
Recommend     Done
new labels
```

## Steps

1. Fetch the issue details:
   ```
   ghx issue view $1
   ```
2. Fetch all available labels:
   ```
   gh label list
   ```
3. Match the issue content to existing labels and apply them:
   ```
   gh issue edit $1 --add-label "<label1>" --add-label "<label2>"
   ```
4. If no existing labels adequately categorize the issue, recommend new labels with suggested names and descriptions.

## Example Usage

**Scenario 1: Bug report**
```
/label-issue 42
```
Issue describes a crash in the login flow. Applies: `bug`, `authentication`. No new labels needed.

**Scenario 2: Feature request with no matching label**
```
/label-issue 100
```
Issue requests a dark mode toggle. No `ui` or `enhancement` label exists. Applies `feature-request` if available, recommends creating a `ui` label.

**Scenario 3: Duplicate issue**
```
/label-issue 55
```
Issue is a known duplicate. Applies `duplicate` label. Recommends closing with a reference to the original.

## Useful Commands Reference

| Command | Description |
|---|---|
| `ghx issue view <issue-number>` | Fetch issue title, body, and current labels (cached) |
| `gh label list` | List all available labels in the repository |
| `gh issue edit <issue-number> --add-label "<label>"` | Apply one or more labels to an issue |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…