Does this skill help with identifying cloud providers?

Yes, it includes keyword mapping for AWS (CAPA), Azure (CAPZ), vSphere (CAPV), and Cloud Director (CAPVCD) to automatically suggest the correct provider label.

What is the difference between Kinds and Areas?

Kinds refer to the type of work (e.g., bug, feature, or epic), while Areas refer to specific product domains like KaaS (Kubernetes-as-a-Service) or the general Platform.

How does the skill handle bug severity?

The skill analyzes keywords like 'outage', 'critical', or 'degraded' to suggest the appropriate impact level, ranging from low to high severity.

Why is only one team label allowed per issue?

Giant Swarm’s taxonomy requires exactly one team label per issue to ensure clear accountability and prevent ambiguity in project tracking and reporting.

Can I use this for non-engineering tasks?

Absolutely. The taxonomy includes functions for marketing, customer success, product strategy, and documentation to support cross-functional work.

Giant Swarm Label Taxonomy

Name: Giant Swarm Label Taxonomy
Author: giantswarm

bygiantswarm

협업 도구

Standardizes GitHub issue categorization across Giant Swarm repositories using a comprehensive 200+ label system.

소개

This skill provides Claude with the specialized knowledge required to accurately tag and organize GitHub issues according to Giant Swarm’s internal standards. It covers specific team assignments, issue types (kinds), cloud providers, and impact levels, ensuring consistency across hundreds of repositories. By utilizing this skill, Claude can automatically identify the correct team, workstream, or product area based on issue content, facilitating better project tracking, automated reporting, and cross-team coordination within the Giant Swarm ecosystem.

주요 기능

Identifies cloud provider context (AWS, Azure, vSphere) from issue descriptions
Enforces 'Exactly One' team label rule for clear issue ownership
Provides standardized labeling patterns for Epics, Stories, and Postmortems
0 GitHub stars
Maps 200+ specialized GitHub labels across seven distinct categories
Detects severity levels and customer mentions to automate impact labeling

사용 사례

Automatically classifying bug reports based on provider and customer impact
Standardizing issue metadata during the creation of new GitHub tickets
Auditing existing repositories to ensure compliance with Giant Swarm taxonomy

소개

주요 기능

Identifies cloud provider context (AWS, Azure, vSphere) from issue descriptions
Enforces 'Exactly One' team label rule for clear issue ownership
Provides standardized labeling patterns for Epics, Stories, and Postmortems
0 GitHub stars
Maps 200+ specialized GitHub labels across seven distinct categories
Detects severity levels and customer mentions to automate impact labeling

사용 사례

Automatically classifying bug reports based on provider and customer impact
Standardizing issue metadata during the creation of new GitHub tickets
Auditing existing repositories to ensure compliance with Giant Swarm taxonomy