glab-schedule

Manage GitLab CI/CD pipeline schedules with cron expressions and target branches.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill glab-schedule-haomingz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glab-schedule
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/gitlab-cli-guide/glab-schedule
Command: npx skills add https://github.com/haomingz/kimi-skills --skill glab-schedule-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitLab CI/CD schedules are often managed manually across multiple projects; this skill automates creation, listing, updating, deleting, and running scheduled pipelines to streamline recurring builds.

Core Features & Use Cases

  • Create, list, update, delete, and run pipeline schedules for a GitLab project.
  • Specify cron expressions and target branches to automate recurring workflows.
  • Manage schedules across repositories and teams with consistent tooling.

Quick Start

Create a new schedule for the main branch with a cron expression, or list and run existing schedules.

Frequently Asked Questions about glab-schedule

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

FAQPage Schema
How do I automate GitLab CI pipeline schedules using the command line?

To automate GitLab CI pipeline schedules via the command line, you can use the glab schedule commands to create, list, update, delete, and trigger pipelines based on cron expressions and target branches.

Can I trigger a scheduled GitLab CI pipeline to run immediately?

Yes, you can trigger a scheduled GitLab CI pipeline to run immediately by executing the scheduled runs programmatically through the command line interface.

How do I manage GitLab CI schedules across multiple repositories?

You can manage GitLab CI schedules across multiple repositories by using the --repo flag and related command line options to handle pipeline configurations for different project scopes.

What is needed to set up recurring GitLab CI builds with cron expressions?

To set up recurring GitLab CI builds, you need to specify cron expressions and target branches when creating a new schedule, ensuring your project uses GitLab CI to automate the recurring workflows.

Does this approach work for updating existing GitLab pipeline schedules?

Yes, this approach works for updating existing GitLab pipeline schedules, as the functionality supports modifying current schedules including updating cron expressions and target branches.