glab-label — Claude Code skill for GitLab labels and setup
The glab-label Claude Code skill manages GitLab labels at project and group level. It responds to requests to create, inspect, edit, or remove labels for issues and merge requests.
MIT 118 installs ★ 51 updated 2026-10-20
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a claude-codeWhat glab-label does
The skill creates, lists, edits, and deletes GitLab labels. It helps place shared labels at group level and workflow-specific ones at project level.
Label lists accept the --page and --per-page options. For a single label, glab label get can return JSON with --output json or -F json. When GitLab provides a total count, the list header uses that total even if the current page shows fewer rows. The skill also covers label colors and descriptions.
What it helps with
- create priority labels shared across group projects
- keep project-specific labels separate from shared ones
- change a label’s color or description
- find and remove deprecated labels
- retrieve one label as JSON
Example prompts for the agent
- Create an orange
priority::highlabel in theengineeringgroup. - List the project labels and save them to
labels.txt. - Change the color of
bugand add the description “Software defect”.
How to install glab-label
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a claude-code2Manually: put the files in place
~/.claude/skills/glab-label/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glab-label/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a codex2Manually: put the files in place
.agents/skills/glab-label/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a cursor2Manually: put the files in place
.cursor/skills/glab-label/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vince-winkintel/gitlab-cli-skills glab-label2Manually: put the files in place
.github/skills/glab-label/SKILL.md1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a gemini-cli2Platform CLI
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-labelManually: put the files in place
.devin/skills/glab-label/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about glab-label
How do I install glab-label in Claude Code?
Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-label -a claude-code. The skill file is at ~/.claude/skills/glab-label/SKILL.md.
What does glab-label do?
It creates, lists, edits, and deletes GitLab labels for a project or group. It can also fetch one label in JSON format.
When should a label belong to a group rather than a project?
Use a group-level label for workflows shared across multiple projects. Keep a project-level label for a workflow specific to one project.
Source text
SKILL.md · MIT
--- name: glab-label description: Manage GitLab labels including create, list, update, and delete operations at project and group level. Use when organizing issues/MRs with labels, creating label taxonomies, or managing label colors/descriptions. Triggers on label, tag, issue label, create label, manage labels. --- # glab label Manage labels at project and group level. ## Quick start ```bash # Create project label glab label create --name bug --color "#FF0000" # Create group label glab label create --group my-group --name priority::high --color "#FF6B00" # List labels glab label list # Update label glab label edit bug --color "#CC0000" --description "Software defects" # Delete label glab label delete bug ``` ## Decision: Project vs Group Labels? ``` Where should this label live? ├─ Used across multiple projects in a group │ └─ Group-level: glab label create --group <group> --name <label> └─ Specific to one project └─ Project-level: glab label create --name <label> ``` **Use group-level labels when:** - You want consistent labeling across all projects in a group - Managing organization-wide workflows - Examples: `priority::high`, `type::bug`, `status::blocked` - Reduces duplication and ensures consistency **Use project-level labels when:** - Label is specific to project workflow - Team wants control over their own labels - Examples: `needs-ux-review`, `deploy-to-staging`, `legacy-code` ## Common workflows ### Creating a label taxonomy **Set up priority labels (group-level):** ```bash glab label create --group engineering --name "priority::critical" --color "#FF0000" glab label create --group engineering --name "priority::high" --color "#FF6B00" glab label create --group engineering --name "priority::medium" --color "#FFA500" glab label create --group engineering --name "priority::low" --color "#FFFF00" ``` **Set up type labels (group-level):** ```bash glab label create --group engineering --name "type::bug" --color "#FF0000" glab label create --group engineering --name "type::feature" --color "#00FF00" glab label create --group engineering --name "type::maintenance" --color "#0000FF" ``` ### Managing project-specific labels **Create workflow labels:** ```bash glab label create --name "needs-review" --color "#428BCA" glab label create --name "ready-to-merge" --color "#5CB85C" glab label create --name "blocked" --color "#D9534F" ``` ### Bulk operations **List all labels to review:** ```bash glab label list --per-page 100 > labels.txt ``` When GitLab supplies a total in its pagination response, the text header reports that real total label count rather than merely the number returned on the current page. Use `--page` and `--per-page` to retrieve additional pages; do not infer that every label is present just because the displayed total is larger than the rows shown. **Delete deprecated labels:** ```bash glab label delete old-label-1 glab label delete old-label-2 ``` ## Related Skills **Using labels:** - See `glab-issue` for applying labels to issues - See `glab-mr` for applying labels to merge requests - Script: `scripts/batch-label-issues.sh` for bulk labeling ## Structured output `glab label get` supports `--output json` / `-F json` for structured output, which is useful for agent automation. ```bash # Get a label with JSON output glab label get <label-id> --output json glab label get <label-id> -F json ``` ## Command reference For complete command documentation and all flags, see [references/commands.md](references/commands.md). **Available commands:** - `create` - Create label (project or group) - `list` - List labels - `edit` - Update label properties - `delete` - Delete label - `get` - View single label details
© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills