mav-bp-cicd-gitlab

Name: mav-bp-cicd-gitlab
Availability: InStock
Author: Thermite

Monitor GitLab CI/CD pipelines and retry failed jobs until they pass.

10|2|Updated Mar 3, 2026

Search Tags:#logs #pipeline #gitlab #retry #ci #monitor

Ready to run

npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd-gitlab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mav-bp-cicd-gitlab
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-bp-cicd-gitlab
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd-gitlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After pushing, monitor GitLab CI/CD pipelines and do not declare work complete until CI passes. This skill implements the platform-specific behaviours defined in the mav-bp-cicd skill.

Core Features & Use Cases

Check CI status and view pipelines for the current branch.
Read failed job logs and retry failed jobs to verify fixes locally.
Enforce a "do not declare work complete" rule until the pipeline passes, and guide remediation steps when failures occur.

Quick Start

After pushing, monitor the pipeline status with glab ci view and only mark work complete when the pipeline passes.

Frequently Asked Questions about mav-bp-cicd-gitlab

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

FAQPage Schema

How do I monitor GitLab CI pipelines after pushing code?▼

To monitor GitLab CI pipelines after pushing, use the glab CLI or GitLab API to observe pipeline status for your current branch and verify successful completion before declaring work done.

What is the best way to view failed GitLab CI job logs and retry them?▼

Viewing failed GitLab CI job logs and retrying them involves using glab ci view to read the failure output, diagnose the issue, and execute a job retry to verify your fixes locally before pushing.

Can I use glab to check GitLab pipeline status for the current branch?▼

Yes, you can use glab to check GitLab pipeline status for the current branch by running glab ci view, which observes pipelines and enforces a no-declare-work-complete rule until the pipeline passes.

Why does my GitLab CI pipeline fail after a push and how do I remediate it?▼

GitLab CI pipeline failures after a push require reading the failed job logs to diagnose the root cause, applying local fixes, and retrying the failed jobs through the GitLab API or glab to confirm remediation.

Does this GitLab CI monitoring approach work without declaring work complete early?▼

Yes, this GitLab CI monitoring approach enforces a strict no-declare-work-complete rule, guiding you through viewing pipelines, reading logs, and retrying failed jobs until the pipeline actually passes.