Managing Repository Labels

Semantic labels organize issues by category—nature, domain, quality, infrastructure, impact—with consistent color assignments. Use gh CLI and Bash scripts to create labels, assign colors via LABEL-COLORS.md, document the taxonomy in .github/LABELS.md, and apply labels to existing issues to establish a standardized triage system.

Audit unlabeled issues and identify duplicates or namespace clashes. Migrate historical issues to new semantic labels, delete obsolete ones, and enforce non-overlapping categories. Document the migration steps and rationale in .github/LABELS.md so contributors follow the new taxonomy consistently.

Refresh labels every 6–12 months during periodic maintenance, after migrations from legacy systems, or when issues show inconsistent labeling. This prevents taxonomy drift, ensures new contributors understand labeling conventions, and keeps issue triage efficient as the repository evolves.

Generate documentation at .github/LABELS.md listing each label, its purpose, color assignment, and usage guidelines. Publish this alongside contribution guidelines so new contributors and maintainers apply labels consistently without manual correction.

Yes. Assign colors semantically—one color per category (e.g., red for bugs, blue for features)—following LABEL-COLORS.md conventions. Color-coded labels make issue lists scannable, reduce cognitive load during triage, and signal priority or type at a glance in GitHub's interface.

This Skill uses gh CLI and Bash scripts to automate label creation, migration, and cleanup. gh CLI is GitHub's official command-line tool and integrates directly with repositories; Bash scripting enables bulk operations and audit workflows without manual label management.