Verified:GitHub

pipeline-monitor

Monitors GitLab CI/CD pipelines, diagnoses failures, applies fixes, and re-pushes until green.

Updated Jul 22, 2026

Search Tags:#devops #ci/cd #auto-fix #gitlab #failure diagnosis #pipeline monitoring #glab cli

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill pipeline-monitor-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pipeline-monitor
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/gitlab-ci/skills/pipeline-monitor
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill pipeline-monitor-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Watching CI pipelines manually and debugging failed jobs wastes developer time. This Skill automates the full loop: it polls a GitLab pipeline to completion, diagnoses failed jobs with sub-agents, proposes and applies fixes, commits, pushes, and repeats until the pipeline passes. ## Core Features & Use Cases - Automated Pipeline Polling: Polls pipeline status via the glab CLI using shell scripts, collapsing long waits into a single tool call with configurable interval and timeout. - Parallel Failure Diagnosis: Launches sub-agents for each failed job to fetch logs, classify failures (lint, test, build, YAML, infrastructure, flaky), and return compact root-cause summaries. - Fix-and-Retry Loop: Applies code fixes, lints modified .gitlab-ci.yml, commits with conventional messages, pushes, detects the new pipeline, and iterates up to a configurable maximum. - Use Case: After pushing a branch, ask the assistant to monitor the pipeline; it watches the run, fixes a rubocop offense and a broken test assertion, pushes the fixes, and confirms the next pipeline passes. ## Quick Start Ask the assistant to monitor the pipeline for the current branch and automatically fix any failures until it passes.

Frequently Asked Questions about pipeline-monitor

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

FAQPage Schema

How do I monitor a GitLab CI pipeline automatically?▼

Provide a pipeline URL, pipeline ID, or branch name, and the skill polls the pipeline using the glab CLI until it reaches a terminal state. With no argument, it detects the current git branch and monitors its latest pipeline.

How to automatically fix failing GitLab CI jobs?▼

The skill launches parallel sub-agents that fetch each failed job's log, classify the failure category, and propose fixes. It then applies the fixes, commits with a conventional message, pushes, and monitors the newly triggered pipeline.

What tool is required to monitor GitLab pipelines from the CLI?▼

The glab CLI (GitLab CLI) must be installed and authenticated via glab auth login. The skill verifies availability with glab --version before starting and stops if it is missing.

Can the pipeline monitor handle flaky tests or infrastructure failures?▼

Flaky failures trigger an offer to retry the job via glab ci retry before attempting code changes. Infrastructure and permission failures are classified as not locally fixable and are only reported.

What are the limitations of automated pipeline fixing?▼

The loop stops after a default of 5 fix iterations or a 30-minute poll timeout. It cannot fix infrastructure, runner, or permission issues, and it stops if the user declines a fix or push.