glab-issue

name	glab-issue
description	Manage GitLab Issues using the glab CLI. Use this skill whenever the user mentions creating, listing, viewing, updating, closing, or commenting on GitLab issues. Trigger on phrases like "create an issue", "list issues", "close issue

GitLab Issue Management

Use glab CLI to manage GitLab issues. Always run glab auth status first if there's any doubt about authentication.

Create an Issue

glab issue create -t "<title>" -d "<description>"
glab issue create -t "<title>" -l <label> -a <username> -m <milestone>
glab issue create -t "<title>" --web   # continue in browser

Key flags:

• -t title (required)
• -d description (- opens editor)
• -l label (repeatable: -l bug -l frontend)
• -a assignee username (repeatable)
• -m milestone name
• --due-date YYYY-MM-DD
• -c confidential
• --weight <n>
• -y skip confirmation

List Issues

glab issue list                         # open issues
glab issue list -a <username>           # by assignee
glab issue list -l <label>             # by label
glab issue list -m <milestone>         # by milestone
glab issue list --search "<keywords>"  # keyword search
glab issue list -c                     # closed only
glab issue list -A                     # all issues
glab issue list -O json                # JSON output
glab issue list -P 50                  # 50 per page

View an Issue

glab issue view <id>
glab issue view <id> --comments
glab issue view <id> -w   # open in browser

Update an Issue

glab issue update <id> -t "<new title>"
glab issue update <id> -l <label>          # add label
glab issue update <id> -u <label>          # remove label
glab issue update <id> -a <username>       # add assignee
glab issue update <id> -a -<username>      # remove assignee
glab issue update <id> -m <milestone>
glab issue update <id> --due-date 2025-12-31
glab issue update <id> --lock-discussion

Close / Reopen

glab issue close <id>
glab issue reopen <id>

Add a Comment

glab issue note <id> -m "<comment text>"

Delete an Issue

glab issue delete <id>

Behavior Guidelines

1. When creating an issue, ask for missing required fields (title). Suggest labels/assignees if context is clear.
2. For list operations, present results as a concise table: ID | Title | State | Assignee | Labels.
3. When the user says "close all issues matching X", use glab issue list -O json | jq to get IDs first, then close in a loop.
4. Prefer --yes / -y to skip interactive prompts in non-interactive contexts.
5. Use -R owner/repo to target a specific repository if not in a git directory.