ci-cd-fix-with-release

Diagnoses and fixes CI/CD pipeline failures, then executes automated version-bumped releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Broken CI/CD pipelines block releases and require tedious manual debugging across workflow files, logs, and test suites. This Skill autonomously diagnoses pipeline failures, applies surgical fixes with root-cause analysis, verifies all quality gates pass, and performs the complete release ceremony including version bumps, changelogs, tags, and GitHub/GitLab release publication. ## Core Features & Use Cases - Autonomous Fix Loop: Runs a local CI/CD runner script iteratively, zeroing in on one failure at a time with 4-part RCA documentation until all jobs exit green. - Local Runner Generation: Scans GitHub Actions, GitLab CI, and other pipeline configs to generate a Python worker-pool runner that mirrors remote CI jobs locally. - Full Release Orchestration: Bumps versions, assembles release notes with install one-liners, updates changelogs and README pins, tags, and publishes releases via gh or glab. - Use Case: A GitHub Actions workflow fails after adding a new linter job. Trigger this Skill to register the job in the local runner, reproduce the failure, fix the code, verify all tests pass, and ship the patched release automatically. ## Quick Start Fix the failing CI/CD pipeline and release a new version once all tests and quality gates pass.

Frequently Asked Questions about ci-cd-fix-with-release

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

FAQPage Schema
How do I automatically fix a failing CI/CD pipeline?

Trigger the fix-and-release workflow to run a local Python runner that mirrors your CI jobs, reproduce each failure, apply minimal code fixes, and loop until every job exits with code 0. Each failure is documented with a 4-part root-cause analysis before fixing.

How to run GitHub Actions jobs locally before pushing?

The Skill generates a local runner script at 03-ai-scripts/06-cicd-local-runner.py by scanning your .github/workflows YAML files, stripping Docker wrappers, and registering each job's commands in a JOBS dictionary executed by a concurrent thread pool.

Does this work with GitLab CI or only GitHub Actions?

It supports GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines, and CircleCI. The configuration scan reads .gitlab-ci.yml, azure-pipelines.yml, bitbucket-pipelines.yml, and .circleci/config.yml in addition to .github/workflows files.

What happens if a CI job times out instead of failing?

Timeouts are treated as slow jobs, not code failures. The runner increases JOB_TIMEOUT_SEC intelligently, such as by 50 percent when elapsed time nears the limit, documents the change in .ai-memory/cicd-issues, and re-runs the job.

When should I not use the automated release workflow?

Do not proceed to release when any quality gate or unit test still fails, when plan tasks from the run remain open, or when the previous changelog entry contains TBD placeholders. The Skill refuses to release until Phase 3 verification passes completely.