gitlab-cli-skillsComprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git...
Install via ClawdBot CLI:
clawdbot install vince-winkintel/gitlab-cli-skillsComprehensive GitLab CLI (glab) command reference and workflows.
# First time setup
glab auth login
# Common operations
glab mr create --fill # Create MR from current branch
glab issue create # Create issue
glab ci view # View pipeline status
glab repo view --web # Open repo in browserThis skill routes to specialized sub-skills by GitLab domain:
Core Workflows:
glab-mr - Merge requests: create, review, approve, mergeglab-issue - Issues: create, list, update, close, commentglab-ci - CI/CD: pipelines, jobs, logs, artifactsglab-repo - Repositories: clone, create, fork, manageProject Management:
glab-milestone - Release planning and milestone trackingglab-iteration - Sprint/iteration managementglab-label - Label management and organizationglab-release - Software releases and versioningAuthentication & Config:
glab-auth - Login, logout, Docker registry authglab-config - CLI configuration and defaultsglab-ssh-key - SSH key managementglab-gpg-key - GPG keys for commit signingglab-token - Personal and project access tokensCI/CD Management:
glab-job - Individual job operationsglab-schedule - Scheduled pipelines and cron jobsglab-variable - CI/CD variables and secretsglab-securefile - Secure files for pipelinesglab-runner-controller - Runner controller and token management (EXPERIMENTAL, admin-only)Collaboration:
glab-user - User profiles and informationglab-snippet - Code snippets (GitLab gists)glab-incident - Incident managementAdvanced:
glab-api - Direct REST API callsglab-cluster - Kubernetes cluster integrationglab-deploy-key - Deploy keys for automationglab-stack - Stacked/dependent merge requestsglab-opentofu - Terraform/OpenTofu state managementUtilities:
glab-alias - Custom command aliasesglab-completion - Shell autocompletionglab-help - Command help and documentationglab-version - Version informationglab-check-update - Update checkerglab-changelog - Changelog generationglab-attestation - Software supply chain securityglab-duo - GitLab Duo AI assistantglab-mcp - Model Context Protocol server for AI assistant integration (EXPERIMENTAL)Use glab when:
Use web UI when:
# Start work on issue
glab issue view 123
git checkout -b 123-feature-name
# Create MR when ready
glab mr create --fill --draft
# Mark ready for review
glab mr update --ready
# Merge after approval
glab mr merge --when-pipeline-succeeds --remove-source-branch# List your review queue
glab mr list --reviewer=@me --state=opened
# Review an MR
glab mr checkout 456
glab mr diff
npm test
# Approve
glab mr approve 456
glab mr note 456 -m "LGTM! Nice work on the error handling."# Check pipeline status
glab ci status
# View failed jobs
glab ci view
# Get job logs
glab ci trace <job-id>
# Retry failed job
glab ci retry <job-id>Need to track work?
āā Yes ā Create issue first (glab issue create)
ā Then: glab mr for <issue-id>
āā No ā Direct MR (glab mr create --fill)Use glab issue create + glab mr for when:
Use glab mr create directly when:
What do you need?
āā Overall pipeline status ā glab ci status
āā Visual pipeline view ā glab ci view
āā Specific job logs ā glab ci trace <job-id>
āā Download build artifacts ā glab ci artifact <ref> <job-name>
āā Validate config file ā glab ci lint
āā Trigger new run ā glab ci run
āā List all pipelines ā glab ci listQuick reference:
glab ci status, glab ci view, glab ci runglab ci trace, glab job retry, glab job viewglab ci artifact (by pipeline) or job artifacts via glab jobWhat's your relationship to the repo?
āā You have write access ā glab repo clone group/project
āā Contributing to someone else's project:
ā āā One-time contribution ā glab repo fork + work + MR
ā āā Ongoing contributions ā glab repo fork, then sync regularly
āā Just reading/exploring ā glab repo clone (or view --web)Fork when:
Clone when:
Where should the label live?
āā Used across multiple projects ā glab label create --group <group>
āā Specific to one project ā glab label create (in project directory)Group-level labels:
Project-level labels:
MR and Issue workflows:
glab-issue to create/track workglab-mr to create MR that closes issuescripts/create-mr-from-issue.sh automates thisCI/CD debugging:
glab-ci for pipeline-level operationsglab-job for individual job operationsscripts/ci-debug.sh for quick failure diagnosisRepository operations:
glab-repo for repository managementglab-auth for authentication setupscripts/sync-fork.sh for fork synchronizationConfiguration:
glab-auth for initial authenticationglab-config to set defaults and preferencesglab-alias for custom shortcutsGenerated Feb 27, 2026
A DevOps engineer uses glab to automate CI/CD pipeline management, including triggering builds, monitoring job statuses, and managing variables. This reduces manual intervention and speeds up deployment cycles in cloud-native environments.
An open-source contributor leverages glab to handle merge requests efficiently, from creation to review and merging. This streamlines collaboration on GitLab-hosted projects, especially when working across multiple repositories.
A project manager utilizes glab to create and update issues, milestones, and labels for sprint planning. This enables quick updates and progress tracking without switching to the web UI, ideal for fast-paced agile teams.
A security engineer employs glab for software attestation and secure file management in CI/CD pipelines. This helps enforce compliance and audit trails, particularly in regulated industries like finance or healthcare.
An infrastructure developer uses glab with OpenTofu/Terraform for state management and cluster integration. This automates infrastructure-as-code workflows and Kubernetes deployments in hybrid cloud setups.
Offer a premium version of glab with enhanced features like advanced analytics, team collaboration tools, and priority support. Revenue comes from monthly or annual subscriptions tailored for enterprise teams.
Provide consulting services to help organizations integrate glab into their existing workflows, including custom script development and training. Revenue is generated through project-based fees and ongoing support contracts.
Distribute glab as a free, open-source tool with basic functionality, while monetizing through paid add-ons like advanced security features, AI-assisted automation (e.g., GitLab Duo integration), and premium templates. Revenue streams include one-time purchases or tiered subscriptions.
š¬ Integration Tip
Integrate glab with existing CI/CD tools like Jenkins or GitHub Actions by using its API capabilities for cross-platform automation, and set up shell aliases to streamline common commands.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.