configure-labels

Standardize GitHub labels to match SDLC conventions across repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the standard label taxonomy in a GitHub repository so that downstream skills (triage-issues, label-issue, prioritize-issues) can classify and manage issues consistently. Idempotent: safe to re-run on a repository that already has some or all labels configured.

Core Features & Use Cases

  • Create missing labels from the standard taxonomy (Type, Area, Platform, Provider, Priority, Triage State, Severity) and align descriptions and colors to project conventions.
  • Update existing labels with correct descriptions and colors when they diverge from the convention, while preserving user-created labels not in the standard set.
  • Remove conflicts with GitHub defaults and report changes to support continuous governance of issue labeling.

Quick Start

Run the configure-labels skill against the target repository to create and align all SDLC labels.

Frequently Asked Questions about configure-labels

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

FAQPage Schema
How do I standardize GitHub issue labels across multiple repositories?

Standardizing GitHub issue labels involves applying a consistent SDLC taxonomy across repositories. This process creates missing labels and updates existing ones with correct descriptions and colors while preserving user-created labels not in the standard set.

Can I re-run label configuration on a repository without duplicating or losing custom labels?

Yes, the label configuration process is idempotent, meaning it is safe to re-run on repositories that already have labels configured. It ensures idempotent changes without removing unknown or user-created labels outside the standard set.

What do I need to configure SDLC labels in my GitHub repository?

To configure SDLC labels, you need gh CLI access and an architectural context file located at .sdlc/context. These prerequisites allow the tool to read project conventions and apply label changes via the GitHub API.

What types of GitHub labels are included in a standard SDLC taxonomy?

A standard SDLC taxonomy includes labels for Type, Area, Platform, Provider, Priority, Triage State, and Severity. These classifications help downstream skills classify and manage issues consistently across the project lifecycle.

How does label standardization handle conflicts with GitHub's default labels?

Label standardization handles conflicts with GitHub defaults by updating or resolving them to match SDLC conventions. It reports all changes to support continuous governance of issue labeling without deleting unknown labels.