About glab-incident
A skill for managing GitLab incidents with glab, including listing, viewing, commenting, subscribing, closing, and reopening incidents. It documents filters, output options, and file attachments for incident comments.
Key features
- 01List and view incidents
- 02Comment with optional file attachments
- 03Subscribe, close, or reopen incidents
- 04Filter lists by assignee and dates
- 05Choose supported list output formats
Use cases
- 01Post an incident update with a dashboard image
- 02List incidents assigned to a person or nobody
- 03Select incident list output for a script
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ vince-winkintel/ gitlab-cli-skills --skill glab-incidentAfter installing, type/glab-incidentin Claude Code to confirm it loaded.
Bundled filesreferences/commands.md
Details
From the project READMEglab incident
Internal notes
glab incident note 123 --internal --message "Incident details for project members" requests an internal note visible only to project members. Verify the target incident and intended audience before posting; internal notes are not a place to store credentials. Incident list uses the shared issue date and assignment filters, including --assignee @none and --assignee @any.
Overview
Complete help from the verified release binary; immutable capture ID
5686d7484maps to the release and archive checksums inVERSION. Only trailing whitespace is removed; indentation, blank lines, wrapping, truncation, and product spelling are preserved.
Incidents track service disruptions and their resolution. List and
view incidents, comment on them, and subscribe, close, or reopen
them.
Use `--repo` to target a project other than the current one.
USAGE
glab incident [command] [--flags]
EXAMPLES
glab incident list
COMMANDS
close [<id> | <url>] [--flags] Close an incident.
list [--flags] List project incidents.
note <incident-id> [--flags] Comment on an incident in GitLab.
reopen [<id> | <url>] [--flags] Reopen a resolved incident.
subscribe <id> Subscribe to an incident.
unsubscribe <id> Unsubscribe from an incident.
view <id> [--flags] Display the title, body, and other information about an incident.
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
Quick start
glab incident --help
# Comment with a local attachment
glab incident note 123 --message "Current dashboard state" --attach ./dashboard.png
glab incident list validates both output selectors before making the request: --output accepts only text or json, while --output-format accepts only details, ids, or urls. The two selectors are mutually exclusive. Treat an immediate “must be one of” error as invalid local input rather than a GitLab API failure.
Attach files to incident comments
The experimental --attach <path> flag uploads a file to the incident's project and appends the returned Markdown reference to the comment. Repeat it for multiple files. An attachment can be the entire comment and skips the editor; --attach - reads the attachment from standard input.
Subcommands
glab incident list uses the API's total count in the text header, separately from the rows on the current page. If the API omits the total, the header shows only the current-page count. This does not fetch extra pages or change the JSON row output.
See references/commands.md for full --help output.