ci-cd-fix

Diagnose and fix CI/CD pipeline failures using a local Python runner and root cause analysis.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill ci-cd-fix-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-fix
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/ci-cd-fix
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill ci-cd-fix-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CI/CD pipelines fail for opaque reasons, and developers waste cycles pushing commits just to see if a fix works on remote runners. This Skill autonomously reproduces pipeline jobs locally, diagnoses each failure with a structured 4-part root cause analysis, and applies surgical fixes until every quality gate exits with code 0. ## Core Features & Use Cases - Local Runner Generation: Scans GitHub Actions, GitLab CI, Azure Pipelines, and other workflow files to generate a Python local runner (06-cicd-local-runner.py) with a concurrent worker pool, timeouts, and consolidated failure logs. - Autonomous Fix Loop: Runs a bounded self-loop that zeroes in on one failure at a time, writes a 4-part RCA (why, how, root cause, code fix) to .ai-memory/memory/issues/, applies a minimal fix, and re-verifies until exit code 0. - Remote Pipeline Diagnostics: Uses gitmap pipeline-ai status with adaptive ETA-based waiting to extract targeted failure lines from remote pipelines without polling loops. - Use Case: A screenshot shows a failing GitHub Actions workflow. The Skill extracts the pipeline name, updates the local runner's JOBS dictionary, reproduces the failure locally, fixes the offending code, and commits everything in one atomic commit. ## Quick Start Ask the AI to fix the failing CI/CD pipeline by running the local runner and resolving each error until all quality gates pass.

Frequently Asked Questions about ci-cd-fix

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

FAQPage Schema
How do I reproduce GitHub Actions failures locally?

Generate a local runner script that mirrors the workflow's jobs by scanning .github/workflows YAML files and translating each run command into a JOBS dictionary. The runner executes jobs concurrently with timeouts and prints full stdout and stderr for every failure.

How to fix CI/CD pipeline failures automatically?

Run the local runner, parse the first failing job's error message, document a 4-part root cause analysis, apply a minimal surgical code fix, and re-run the runner. Repeat this loop for each remaining failure until the runner exits with code 0.

Can Docker-based CI steps run locally without Docker?

Yes, by treating the host machine as the container. Strip docker run wrappers and execute the inner commands directly, replacing Docker env injection with Python os.environ assignments, while skipping registry login and image push steps.

Why should CI lint checks never be disabled to pass a pipeline?

Disabling linters with flags like continue-on-error or || true hides real defects and produces false green builds. The correct approach is to fix the underlying source code so every quality gate passes legitimately.

What is a 4-part root cause analysis for build failures?

It documents why the failure happened architecturally, how the execution flow triggered it, the exact file and line responsible, and a before/after code fix. Each RCA is stored as a Markdown file for future reference.