labels

Classify GitHub issues using a category:value label taxonomy and apply labels via GitHub CLI.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/davidsneighbour/clerkwork --skill labels-davidsneighbour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: labels
Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/labels
Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill labels-davidsneighbour

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Issue triage often produces inconsistent labels across repositories, making it hard to filter by type, status, priority, or resolution. This Skill enforces a canonical category:value label taxonomy so every open and closed issue carries exactly the right lifecycle labels. ## Core Features & Use Cases - Taxonomy-based classification: Selects exactly one type, status, and priority for open issues, and one resolution for closed issues, following strict lifecycle invariants defined in references/label-taxonomy.yml. - Label application via GitHub CLI: Computes add/remove/keep diffs against an issue's existing labels and applies changes with gh, while preserving labels outside the managed namespaces. - Taxonomy provisioning script: scripts/label-manager.sh creates or updates the canonical label set in one or more repositories, with dry-run, audit-only, and --clear modes. - Use Case: When triaging a newly reported bug, the Skill reads the issue text, recommends type:bug, status:unconfirmed, and prio:low, explains any uncertainty, and applies the labels once confirmed. ## Quick Start Use the labels skill to analyze this issue and recommend the correct type, status, and priority labels from the repository taxonomy.

Frequently Asked Questions about labels

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

FAQPage Schema
How do I classify GitHub issues with a consistent label taxonomy?▼

Read the issue title, body, and state, then select exactly one type, one status, and one priority for open issues, or one resolution for closed issues, using the category:value taxonomy in references/label-taxonomy.yml. Apply changes with GitHub CLI after comparing against existing labels.

How to create a standard set of issue labels across multiple GitHub repositories?▼

Run scripts/label-manager.sh with --repo OWNER/REPO for each repository. It defaults to dry-run mode; add --apply to create or update the canonical labels, and --audit-only to inspect the current label situation without changes.

What labels should an open issue versus a closed issue have?▼

An open issue must have exactly one type, one status, one prio, and zero or more meta labels. A closed issue must have exactly one type and one resolution, with all status, prio, and meta labels removed.

Does the label-manager script delete existing repository labels?▼

No, by default it only creates or updates canonical labels and never deletes or renames others. The optional --clear flag deletes every existing label before recreating the taxonomy, and only works together with --apply.

Can this label taxonomy be used with GitLab or other git hosts?▼

The classification model is host-agnostic, but the implementation targets GitHub through the gh CLI. Extending to another provider requires adapting scripts/label-manager.sh and the apply steps to that provider's label API.