Verified:GitHub

autofix-ci-job

Diagnose and fix failing GitLab CI jobs with automated polling.

Updated Jan 14, 2022

Search Tags:#CI/CD #pipeline management #GitLab #CI automation #job fixing

One-click install

npx skills add https://github.com/alexmarucci/dotfiles --skill autofix-ci-job

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: autofix-ci-job
Source: https://github.com/alexmarucci/dotfiles/tree/main/claude/skills/autofix-ci-job
Command: npx skills add https://github.com/alexmarucci/dotfiles --skill autofix-ci-job

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of fixing failing GitLab CI jobs, significantly reducing the time and effort spent on manual troubleshooting and maintenance.

Core Features & Use Cases

Automated Troubleshooting: Identifies issues in failing CI jobs and applies fixes.
Efficient Polling: Continuously polls for job status changes and stops once successful.
Customizable Workflow: Allows users to input pipeline IDs or detect them from the current branch.
Use Case: Ideal for development teams with multiple CI jobs, reducing the need for manual intervention and allowing developers to focus on core tasks.

Quick Start

Use the autofix-ci-job skill with a specific pipeline ID, or let it detect the latest failed pipeline from the current branch.

Frequently Asked Questions about autofix-ci-job

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

FAQPage Schema

How do I automate fixing failing GitLab CI jobs?▼

Yes, you can resolve failing GitLab CI pipelines automatically by providing a specific pipeline ID or letting the Skill detect the latest failed pipeline from your current branch. It then applies fixes and polls for job status changes continuously.

Do I need the glab CLI to automate GitLab CI job troubleshooting?▼

Yes, the glab CLI is required to run this GitLab CI automation. It uses glab to query pipeline statuses, diagnose failing jobs, apply fixes, and poll for successful completion within your GitLab environment.

What is the best way to continuously poll GitLab pipeline status until a job succeeds?▼

The best way to poll GitLab pipeline status is using an automated CI job fixing workflow. This Skill monitors job status changes after applying fixes and automatically stops the polling process once the targeted pipeline job becomes successful.

Can I target a specific pipeline ID for CI automation instead of detecting the latest failure?▼

Yes, you can target a specific pipeline ID for CI automation. The workflow allows you to input a pipeline ID to troubleshoot, or it can automatically detect the latest failed pipeline from your current Git branch.

Why does automated CI job fixing stop polling before the pipeline succeeds?▼

Automated CI job fixing stops polling before the pipeline succeeds if it cannot diagnose or apply a valid fix to the failing GitLab CI job. The polling mechanism terminates when the job status changes to successful or no fix can be applied.