glab-ci

name	glab-ci
description	Manage GitLab CI/CD pipelines using the glab CLI. Use this skill whenever the user mentions pipelines, CI jobs, build status, pipeline logs, triggering a pipeline, retrying a failed pipeline, or validating .gitlab-ci.yml. Trigger on phrases like "check pipeline status", "why did the build fail", "trigger a pipeline", "watch CI logs", "lint the CI config", or anything related to GitLab CI/CD.

GitLab CI/CD Pipeline Management

Use glab CLI to manage GitLab CI/CD pipelines and jobs.

List Pipelines

glab ci list                            # recent pipelines on current branch
glab ci list -r <branch>               # specific branch
glab ci list -s <status>               # filter: running|pending|success|failed|canceled
glab ci list --source push             # filter by trigger source
glab ci list -O json

View Pipeline (Interactive)

glab ci view                   # latest pipeline on current branch
glab ci view <pipeline-id>

The interactive view lets you navigate jobs, see status, and trigger retries.

Pipeline Status

glab ci status                 # status of latest pipeline
glab ci status -r <branch>

Trigger a Pipeline

glab ci run                              # run for current branch
glab ci run -b <branch>                 # specific branch
glab ci run -v KEY=value                # pass variables
glab ci run -v ENV=staging -v DEBUG=1

Retry a Failed Pipeline

glab ci retry <pipeline-id>

Cancel a Pipeline

glab ci cancel <pipeline-id>

View Job Logs (Live Trace)

glab ci trace                  # interactive job picker
glab ci trace <job-id>         # specific job

Use trace to stream live logs — useful for debugging long-running jobs.

Validate CI Config

glab ci lint                   # validate .gitlab-ci.yml in current directory
glab ci lint <file>            # validate a specific file

Delete a Pipeline

glab ci delete <pipeline-id>

Behavior Guidelines

1. Debugging failures: When a pipeline fails, use glab ci view to identify the failed jobs, then glab ci trace <job-id> to stream the logs.
2. Default branch: Most commands default to the current branch — specify -r <branch> when working on a different branch.
3. Lint before push: Suggest glab ci lint whenever the user edits .gitlab-ci.yml.
4. Status check: For a quick "is CI green?" question, use glab ci status rather than the full view.
5. JSON output: Use -O json and pipe through jq when the user needs to script pipeline queries.