home / skills / openclaw / skills / glab-milestone

This skill helps you manage glab milestones efficiently by executing create, delete, edit, get, and list commands for groups and projects.

npx playbooks add skill openclaw/skills --skill glab-milestone

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.0 KB
---
name: glab-milestone
description: Use when working with glab milestone commands.
---

# glab milestone

## Overview

```

  Manage group or project milestones.                                                                                   
         
  USAGE  
         
    glab milestone <command> [command] [--flags]  
            
  COMMANDS  
            
    create [--flags]  Create a group or project milestone.
    delete [--flags]  Delete a group or project milestone.
    edit [--flags]    Edit a group or project milestone.
    get [--flags]     Get a milestones via an ID for a project or group.
    list [--flags]    Get a list of milestones for a project or group.
         
  FLAGS  
         
    -h --help         Show help for this command.
    -R --repo         Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.
```

## Quick start

```bash
glab milestone --help
```

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

Overview

This skill provides command-line access to manage GitLab group and project milestones via glab. It wraps common milestone operations—create, edit, delete, get, and list—so you can automate and script milestone workflows. Use it to inspect or modify milestones across repositories or groups with optional repo selection flags.

How this skill works

The skill invokes glab milestone subcommands to perform CRUD operations on milestones. It accepts flags such as --repo to target a specific project or group and forwards standard glab help and options. Commands return the milestone data or operation status suitable for scripting and automation.

When to use it

  • Creating a new milestone for a project or group from CI or scripts
  • Updating milestone titles, descriptions, or due dates centrally
  • Removing obsolete milestones across multiple repositories
  • Listing milestones for reporting or synchronization tasks
  • Fetching a single milestone by ID for conditional automation

Best practices

  • Always run glab milestone --help during initial use to review available flags and examples
  • Use the --repo flag to explicitly target the intended project or group to avoid accidental changes
  • Script idempotent operations: check for existing milestones before creating duplicates
  • Use descriptive titles and stable due dates so automation can reliably match milestones
  • Capture command output and check exit codes when running from CI to handle failures

Example use cases

  • Create a release milestone in CI after tagging a version
  • Edit milestone due dates in bulk when a release schedule shifts
  • Delete test or temporary milestones created during experimentation
  • List all open milestones across a group for status dashboards
  • Fetch a milestone by ID to attach it to issue or merge request templates

FAQ

Do I need GitLab credentials to run these commands?

Yes. glab requires authentication to access GitLab APIs. Ensure you have a valid token or are logged in with glab auth before running commands.

Can I target a different repository than the current directory?

Yes. Use the -R or --repo flag with OWNER/REPO, GROUP/NAMESPACE/REPO, a full URL, or a Git URL to select another repository.

How do I get full help for a specific subcommand?

Run glab milestone <command> --help (for example glab milestone create --help) to see flags and usage for that subcommand.