glab-quick-actions

Batch update GitLab issues and merge requests via glab CLI quick actions.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-quick-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glab-quick-actions
Source: https://github.com/ProyectoG007/Skill.bat/tree/main/scripts/05_Dev_Tools/07.%20gitlab-cli-skills-1.11.0/glab-quick-actions
Command: npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-quick-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines GitLab issue and merge request management by allowing you to execute complex state changes and updates using simple text-based commands directly from your command line.

Core Features & Use Cases

  • Batch Operations: Apply multiple changes (assignees, labels, milestones, time tracking) in a single command, reducing API calls and saving time.
  • Advanced Workflow Automation: Trigger actions not directly exposed by standard glab commands, such as setting epics, moving issues between boards, or promoting issues to incidents.
  • Use Case: Triage a new bug report by assigning it to yourself, adding bug and priority::high labels, and setting the milestone to "Sprint 5" all with one command.

Quick Start

Use the glab-quick-actions skill to assign issue 123 to @alice and add the ~bug label.

Frequently Asked Questions about glab-quick-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run GitLab quick actions from the command line?

You can run GitLab quick actions via the command line using the glab CLI, which parses text-based slash commands to apply assignees, labels, milestones, and state changes to issues and merge requests.

Can I batch update GitLab issues and merge requests in a single command?

Yes, you can batch update GitLab issues and merge requests in a single command by combining multiple quick actions like adding labels and setting milestones through glab CLI, reducing API calls.

Do I need the glab CLI installed to use GitLab quick actions for issue tracking?

Yes, the glab CLI is a required dependency to use GitLab quick actions for issue tracking, as this Skill leverages it for efficient API interaction and atomic operations.

What's the best way to triage GitLab bugs using CLI automation?

The best way to triage GitLab bugs using CLI automation is executing batch quick actions via glab CLI, allowing you to assign issues, add priority labels, and set milestones simultaneously to streamline triage.

What GitLab workflow automations are available through glab quick actions?

Available GitLab workflow automations through glab quick actions include setting epics, moving issues between boards, promoting issues to incidents, time tracking, and managing relations via text-based slash commands.

Why use text-based slash commands instead of standard glab commands for GitLab state management?

Text-based slash commands are used for GitLab state management instead of standard glab commands to trigger advanced actions not otherwise exposed, such as setting epics or promoting issues to incidents, enabling atomic operations.