label-issue

Read a GitHub issue and apply relevant existing labels.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill label-issue-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: label-issue
Source: https://github.com/tomzx/agents/tree/main/skills/label-issue
Command: npx skills add https://github.com/tomzx/agents --skill label-issue-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue triage often slows down work when issues lack the right labels or labels become inconsistent. This skill automatically labels issues by analyzing the issue content and applying the most relevant existing labels to improve categorization and routing.

Core Features & Use Cases

  • Reads the issue's title and body to determine relevant existing labels.
  • Applies matched labels to streamline triage and issue routing.
  • Recommends new labels when current labels are insufficient and can propose names and descriptions for future use.

Quick Start

Label issue number <issue-number> by analyzing its title and body and applying the most relevant existing labels.

Frequently Asked Questions about label-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically apply labels to GitHub issues for triage?

Automatically label GitHub issues by reading the issue title and body to determine and apply the most relevant existing labels, streamlining categorization and routing. It requires gh CLI authentication and repository context.

Can I automatically categorize GitHub bugs and features without manual review?

Yes, you can categorize GitHub bugs and features by analyzing issue content and matching it against existing repository labels. The skill handles common triage scenarios like bugs, features, and duplicates within the current context.

What is the best way to manage inconsistent labels across GitHub repository issues?

Managing inconsistent GitHub issue labels involves reading issue content and applying the most relevant existing labels. This skill automates that process to improve categorization and routing without manual intervention.

Do I need gh CLI authentication to automate issue labeling?

Yes, gh CLI authentication is required to automate issue labeling. The skill needs repository context and permission to fetch and edit issue labels to apply the matched categories.

What happens if existing repository labels are insufficient for an issue?

When existing repository labels are insufficient, the skill recommends new labels. It can propose names and descriptions for future use to better categorize the current issue content.