label-manager

Audit GitHub issues for missing, deprecated, or inconsistent labels.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill label-manager-cmbays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: label-manager
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/label-manager
Command: npx skills add https://github.com/cmbays/mokumo --skill label-manager-cmbays

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that GitHub issues are consistently and accurately labeled, preventing confusion, improving filtering, and maintaining a clean project backlog.

Core Features & Use Cases

  • Audit Labels: Scans open issues for missing required labels, deprecated labels, incorrect separators, and invalid values.
  • Suggest Fixes: Proposes specific label changes to correct identified hygiene issues.
  • Sync Check: Compares current GitHub labels against organizational standards to report drift.
  • Use Case: Before a major release, run the label manager in audit mode to ensure all bugs and features are correctly tagged with types and priorities, making it easier to prioritize and track work.

Quick Start

Run the label manager in audit mode to check all open issues for label hygiene.

Frequently Asked Questions about label-manager

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

FAQPage Schema
How do I audit GitHub issues for missing or deprecated labels?

To audit GitHub issues for missing or deprecated labels, run the label manager in Audit mode to detect missing required labels, wrong separators, deprecated labels, and invalid values. It then proposes specific fixes to correct identified label hygiene issues across your project backlog.

What is GitHub taxonomy drift and how do I check for it?

GitHub taxonomy drift occurs when repository labels diverge from organizational standards. Run the label manager in Sync Check mode to compare current GitHub labels against canonical standards and generate a report detailing the drift and inconsistencies found.

Do I need gh CLI authentication to enforce label consistency?

Yes, you need gh CLI authentication to enforce label consistency. The label manager requires gh CLI access to interact with your GitHub repository, along with access to the CLAUDE.md file for project context to properly audit and classify issues.

Can I get label suggestions for a single GitHub issue?

Yes, you can get label suggestions for a single GitHub issue by running the label manager in Classify mode. This mode analyzes an individual issue and proposes specific label changes to correct any identified hygiene problems or taxonomy drift.

What's the best way to ensure GitHub label consistency before a major release?

The best way to ensure GitHub label consistency before a release is to run the label manager in Audit mode. This scans all open issues to verify that bugs and features are correctly tagged with types and priorities, making it easier to prioritize and track work.

What are the limitations of automating GitHub label taxonomy enforcement?

Limitations of automating GitHub label taxonomy enforcement include strict dependency on gh CLI authentication and access to CLAUDE.md for project context. The label manager operates strictly within Audit, Classify, and Sync Check modes, limiting bulk actions outside these defined scopes.