issue-labeller

Enforce a strict type-and-area GitHub issue label taxonomy via the GitHub CLI.

Updated Aug 23, 2026

Search Tags:#automation #github #triage #taxonomy #issue-tracking #project-hygiene

Ready to run

npx skills add https://github.com/drdanmaggs/claude-skills --skill issue-labeller

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-labeller
Source: https://github.com/drdanmaggs/claude-skills/tree/main/skills/issue-labeller
Command: npx skills add https://github.com/drdanmaggs/claude-skills --skill issue-labeller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the problem of repository rot caused by inconsistent, redundant, or missing issue labels, which makes project tracking and triage difficult.

Core Features & Use Cases

Taxonomy Enforcement: Applies a strict, single-type label system with optional area labels to ensure every issue is categorized correctly.
Backlog Retrofitting: Automatically audits and re-labels large, unorganized backlogs to match a canonical standard.
Consolidation: Identifies and merges redundant labels while preserving issue assignments, ensuring the label list remains lean and meaningful.

Quick Start

Ask the issue labeller to audit the current repository and retrofit the unlabelled backlog to match the canonical taxonomy.

Frequently Asked Questions about issue-labeller

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

FAQPage Schema

How do I automate GitHub issue triage and fix inconsistent labels in my repository?▼

Automating GitHub issue triage involves applying a strict type-and-area taxonomy to standardize repository labels. This process audits unlabelled backlogs, applies canonical labels, and consolidates redundant tags to ensure consistent project tracking and hygiene.

What is the best way to consolidate redundant GitHub issue labels without losing assignments?▼

Consolidating redundant GitHub issue labels requires auditing existing tags and merging duplicates into a canonical standard. This process preserves existing issue assignments while ensuring the repository label list remains lean and meaningful.

Can I retrofit an unorganized GitHub backlog to match a strict label taxonomy?▼

Yes, you can retrofit unorganized GitHub backlogs by auditing open and closed issues and applying a canonical label taxonomy. This enforces a strict single-type label system with optional area labels to categorize every issue correctly.

Do I need the GitHub CLI to perform repository-wide label synchronization?▼

Yes, the GitHub CLI is required to perform repository-wide label synchronization and issue metadata updates. It provides the necessary API access to enforce the strict type-and-area structure across both open and closed issues.

Why does inconsistent issue labeling make project tracking difficult?▼

Inconsistent issue labeling causes repository rot by making it hard to filter and triage work. Applying a strict, single-type label system with optional area labels solves this by ensuring every issue is categorized correctly for reliable project tracking.