setup-labels

Creates and updates GitHub repository labels from the triage taxonomy using the gh CLI.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/PVMalove/claude-agent-harness --skill setup-labels-pvmalove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-labels
Source: https://github.com/PVMalove/claude-agent-harness/tree/main/skills/first-party/pvmalove/setup-labels
Command: npx skills add https://github.com/PVMalove/claude-agent-harness --skill setup-labels-pvmalove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitHub issue commands like gh issue edit --add-label fail when a label does not exist yet, because gh never auto-creates labels. This Skill provisions every label the repo's triage taxonomy needs upfront, so triage, spec, ticket, and implementation workflows never break on a missing label. ## Core Features & Use Cases - Taxonomy-driven label creation: Reads label names and hex colors from docs/agents/triage-labels.md, covering workflow states, execution modes (hitl/afk), and wayfinder labels. - Idempotent application: Runs gh label create --force so existing labels get color updates instead of errors, leaving issues that already carry them untouched. - Safe mutation discipline: Shows the full plan and asks for maintainer confirmation before touching shared GitHub state. - Use Case: Before running triage or ticket workflows in a freshly set up repository, execute this once so every workflow::*, hitl/afk, and wayfinder:* label exists with the correct color. ## Quick Start Ask the agent to set up the GitHub labels for this repository from the triage taxonomy before running any triage or ticket workflows.

Frequently Asked Questions about setup-labels

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

FAQPage Schema
How do I create GitHub labels from the command line?▼

Use gh label create with a name and --color flag for each label. Adding --force makes the command idempotent, updating the color of an existing label instead of failing.

Why does gh issue edit --add-label fail with a missing label error?▼

The gh CLI never auto-creates labels, so adding a label that does not exist in the repository fails. Create the label first with gh label create, then attach it to issues or pull requests.

Does gh label create --force affect issues already using the label?▼

No. The --force flag only updates the label's color when it already exists and leaves everything else untouched. Issues already carrying the label are unaffected.

When should I run repository label setup?▼

Run it once per repository before first using any workflow that applies labels, such as triage, spec creation, ticket slicing, or implementation flows. It requires the taxonomy file docs/agents/triage-labels.md to exist.

Can I update label colors without recreating labels?▼

Yes. Running gh label create with --force and a new hex color updates the existing label's color in place without deleting it or affecting issues that reference it.