gitlab-milestone

GitLab milestone operations. ALWAYS use this skill when user wants to: (1) list milestones, (2) create new milestones, (3) manage sprints or iterations.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "gitlab-milestone" with this command: npx skills add grandcamel/gitlab-assistant-skills/grandcamel-gitlab-assistant-skills-gitlab-milestone

Milestone Skill

Milestone management operations for GitLab using the glab CLI.

Quick Reference

OperationCommandRisk
List milestonesglab milestone list-
Create milestoneglab milestone create <title>⚠️

Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger

When to Use This Skill

ALWAYS use when:

  • User wants to manage project milestones
  • User mentions "milestone", "sprint", "iteration", "release planning"
  • User wants to organize work into time-boxed periods

NEVER use when:

  • User wants to assign milestones to issues (use gitlab-issue)
  • User wants to create releases (use gitlab-release)

Available Commands

List Milestones

glab milestone list [options]

Options:

FlagDescription
-s, --state=<state>Filter by state: active, closed, all
-P, --per-page=<n>Results per page
--allGet all milestones

Examples:

# List active milestones
glab milestone list

# List all milestones including closed
glab milestone list --state=all

# List closed milestones
glab milestone list --state=closed

# List with more results
glab milestone list --per-page=50

Create Milestone

glab milestone create <title> [options]

Options:

FlagDescription
-d, --description=<desc>Milestone description
--due-date=<date>Due date (YYYY-MM-DD format)
--start-date=<date>Start date (YYYY-MM-DD format)

Examples:

# Create simple milestone
glab milestone create "Sprint 1"

# Create with description
glab milestone create "Q1 Release" \
  -d "Features planned for Q1 2024 release"

# Create with dates
glab milestone create "Sprint 5" \
  --start-date=2024-02-01 \
  --due-date=2024-02-14 \
  -d "Two-week sprint"

# Create release milestone
glab milestone create "v2.0.0" \
  --due-date=2024-03-15 \
  -d "Major version 2.0 release"

Common Workflows

Workflow 1: Sprint Planning

# 1. Create new sprint milestone
glab milestone create "Sprint 12" \
  --start-date=2024-03-01 \
  --due-date=2024-03-14 \
  -d "Sprint 12 goals:
- Complete authentication feature
- Fix critical bugs
- Improve test coverage"

# 2. Assign issues to milestone
glab issue update 101 -m "Sprint 12"
glab issue update 102 -m "Sprint 12"
glab issue update 103 -m "Sprint 12"

# 3. View sprint issues
glab issue list --milestone="Sprint 12"

Workflow 2: Release Planning

# 1. List current milestones
glab milestone list

# 2. Create release milestone
glab milestone create "Release 1.5" \
  --due-date=2024-04-01 \
  -d "Version 1.5 release including:
- New dashboard
- Performance improvements
- Bug fixes from user feedback"

# 3. Associate issues
glab issue list --label="release-1.5" | while read issue; do
  glab issue update $issue -m "Release 1.5"
done

Workflow 3: Review Sprint Progress

# 1. List sprint milestones
glab milestone list --state=active

# 2. Check open issues in sprint
glab issue list --milestone="Sprint 12" --state=opened

# 3. Check closed issues
glab issue list --milestone="Sprint 12" --state=closed

# 4. Check MRs in sprint
glab mr list --milestone="Sprint 12"

Milestone Naming Conventions

Common patterns for milestone names:

PatternExampleUse Case
Sprint NSprint 1, Sprint 2Agile sprints
YYYY-QN2024-Q1, 2024-Q2Quarterly planning
vX.Y.Zv1.0.0, v2.1.0Version releases
YYYY-MM2024-03, 2024-04Monthly cycles
Feature Name"User Authentication"Feature-based milestones

Troubleshooting

IssueCauseSolution
Authentication failedInvalid/expired tokenRun glab auth login
Milestone not foundWrong name or closedCheck with glab milestone list --state=all
Invalid dateWrong formatUse YYYY-MM-DD format
Permission deniedNot maintainerNeed maintainer+ role

Related Documentation

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

gitlab-mr

No summary provided by upstream source.

Repository SourceNeeds Review
General

gitlab-ci

No summary provided by upstream source.

Repository SourceNeeds Review
General

gitlab-group

No summary provided by upstream source.

Repository SourceNeeds Review
General

gitlab-issue

No summary provided by upstream source.

Repository SourceNeeds Review