gitlab-label
GitLab label operations. ALWAYS use this skill when user wants to: (1) list project labels, (2) create new labels, (3) manage label colors and descriptions.
What this skill does
# Label Skill Label management operations for GitLab using the `glab` CLI. ## Quick Reference | Operation | Command | Risk | |-----------|---------|:----:| | List labels | `glab label list` | - | | Create label | `glab label create <name>` | ⚠️ | **Risk Legend**: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger ## When to Use This Skill **ALWAYS use when:** - User wants to manage project labels - User mentions "label", "tag" (for categorization), "category" - User wants to organize issues or MRs **NEVER use when:** - User wants to apply labels to issues/MRs (use gitlab-issue or gitlab-mr) - User wants to manage git tags (use git commands or gitlab-release) ## Available Commands ### List Labels ```bash glab label list [options] ``` **Options:** | Flag | Description | |------|-------------| | `-P, --per-page=<n>` | Results per page | | `--all` | Get all labels | **Examples:** ```bash # List all project labels glab label list # List with more results glab label list --per-page=100 ``` ### Create Label ```bash glab label create <name> [options] ``` **Options:** | Flag | Description | |------|-------------| | `-c, --color=<color>` | Label color (hex format, e.g., #ff0000) | | `-d, --description=<desc>` | Label description | **Examples:** ```bash # Create label with default color glab label create "needs-review" # Create label with color glab label create "bug" -c "#ff0000" # Create label with color and description glab label create "priority::high" \ -c "#dc3545" \ -d "High priority items requiring immediate attention" # Create scoped label glab label create "status::in-progress" \ -c "#ffc107" \ -d "Work in progress" ``` ## Common Label Patterns ### Priority Labels ```bash glab label create "priority::critical" -c "#dc3545" -d "Must fix immediately" glab label create "priority::high" -c "#fd7e14" -d "Fix in current sprint" glab label create "priority::medium" -c "#ffc107" -d "Fix soon" glab label create "priority::low" -c "#28a745" -d "Nice to have" ``` ### Type Labels ```bash glab label create "type::bug" -c "#d73a4a" -d "Something isn't working" glab label create "type::feature" -c "#0366d6" -d "New feature request" glab label create "type::docs" -c "#0075ca" -d "Documentation" glab label create "type::refactor" -c "#6f42c1" -d "Code refactoring" ``` ### Status Labels ```bash glab label create "status::backlog" -c "#6c757d" -d "In backlog" glab label create "status::ready" -c "#17a2b8" -d "Ready to start" glab label create "status::in-progress" -c "#ffc107" -d "Work in progress" glab label create "status::review" -c "#007bff" -d "In review" glab label create "status::done" -c "#28a745" -d "Completed" ``` ### Workflow Labels ```bash glab label create "needs-review" -c "#d876e3" -d "Needs code review" glab label create "needs-design" -c "#fbca04" -d "Needs design input" glab label create "blocked" -c "#b60205" -d "Blocked by external dependency" glab label create "help-wanted" -c "#008672" -d "Looking for contributors" ``` ## GitLab Scoped Labels GitLab supports scoped labels using the `::` separator: ``` priority::high status::in-progress type::bug ``` Only one label per scope can be applied to an issue/MR, making them mutually exclusive. ## Common Workflows ### Workflow 1: Set Up New Project Labels ```bash # Create priority labels glab label create "priority::critical" -c "#dc3545" glab label create "priority::high" -c "#fd7e14" glab label create "priority::medium" -c "#ffc107" glab label create "priority::low" -c "#28a745" # Create type labels glab label create "type::bug" -c "#d73a4a" glab label create "type::feature" -c "#0366d6" glab label create "type::docs" -c "#0075ca" ``` ### Workflow 2: Apply Labels to Issues ```bash # List available labels glab label list # Create issue with labels glab issue create -t "Fix login bug" -l "type::bug,priority::high" # Update issue labels glab issue update 42 -l "status::in-progress" ``` ## Color Reference Common colors for labels: | Color | Hex | Use For | |-------|-----|---------| | Red | `#dc3545` | Bugs, critical, blocked | | Orange | `#fd7e14` | High priority, warning | | Yellow | `#ffc107` | Medium priority, in-progress | | Green | `#28a745` | Done, low priority, good first issue | | Blue | `#007bff` | Features, info, review | | Purple | `#6f42c1` | Refactor, enhancement | | Gray | `#6c757d` | Backlog, wontfix | ## Troubleshooting | Issue | Cause | Solution | |-------|-------|----------| | Authentication failed | Invalid/expired token | Run `glab auth login` | | Label already exists | Duplicate name | Use different name or update existing | | Invalid color | Wrong format | Use hex format: #RRGGBB | | Permission denied | Not maintainer | Need maintainer+ role | ## Related Documentation - [Safeguards](../shared/docs/SAFEGUARDS.md) - [Quick Reference](../shared/docs/QUICK_REFERENCE.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.