glab-milestone

name	glab-milestone
description	Manage GitLab milestones using the glab CLI. Use this skill whenever the user wants to create, list, view, edit, or delete milestones in a GitLab project. Trigger on phrases like "create a milestone", "set a sprint milestone", "list active milestones", "update milestone due date", "close a milestone", or any GitLab milestone management task.

GitLab Milestone Management

Use glab CLI to create and manage project milestones for tracking issue and MR progress.

Create a Milestone

glab milestone create --title "<title>"
glab milestone create --title "v1.2" --description "Version 1.2 release"
glab milestone create --title "Sprint 5" --due-date 2025-06-30
glab milestone create --title "Q3 2025" --start-date 2025-07-01 --due-date 2025-09-30

Key flags:

• --title milestone title (required)
• --description description
• --due-date YYYY-MM-DD
• --start-date YYYY-MM-DD

List Milestones

glab milestone list                    # active milestones
glab milestone list --state active
glab milestone list --state closed
glab milestone list --state all
glab milestone list -O json

View a Milestone

glab milestone get <id>
glab milestone get "<title>"

Edit a Milestone

glab milestone edit <id> --title "<new title>"
glab milestone edit <id> --due-date 2025-12-31
glab milestone edit <id> --description "<updated description>"

Delete a Milestone

glab milestone delete <id>

Behavior Guidelines

1. Dates: Use YYYY-MM-DD format consistently. If the user gives a relative date ("end of next month"), convert it before running the command.
2. Naming conventions: Suggest versioned names (e.g., v1.2, v2.0) for release milestones and sprint names (e.g., Sprint 5, 2025-W23) for agile workflows.
3. Linking: Remind the user that milestones can be assigned to issues (glab issue update <id> -m <milestone>) and MRs to track progress.
4. Closing milestones: GitLab closes milestones through the UI or API; use glab milestone edit to update state if needed.