che-ci-fixer

Diagnoses and fixes failing GitHub Actions CI runs by classifying root causes and implementing minimal fixes.

Updated May 12, 2026
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-ci-fixer-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-ci-fixer
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-ci-fixer
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-ci-fixer-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Failing CI pipelines block pull requests and waste engineering time on manual log digging. This Skill automates the diagnosis of failing GitHub Actions runs, classifies the root cause, and implements verified fixes so developers can get builds green again without guesswork. ## Core Features & Use Cases - Failure Identification: Accepts a PR URL or Actions run URL and uses the GitHub CLI to enumerate failing jobs and steps with their logs. - Root Cause Classification: Categorizes each failure into one of nine types (build, lint, test, flaky, dependency, CI config, infra, migration, test mismatch) with a priority-ordered decision table. - Verified Fix Workflow: Reproduces failures locally in a worktree, applies a minimal fix, confirms the check passes, then pushes with conventional commits and re-triggers the run. - Use Case: A teammate pastes a PR link whose checks are red. The Skill pulls the failing job logs, identifies a lockfile sync error (R5), runs corepack pnpm install, commits the updated lockfile, and reports the fix with a link to the re-run. ## Quick Start Paste a failing GitHub PR or Actions run URL and ask the assistant to diagnose and fix the CI failure.

Frequently Asked Questions about che-ci-fixer

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

FAQPage Schema
How do I fix a failing GitHub Actions CI run automatically?▼

Provide a PR URL or Actions run URL, and the workflow uses the GitHub CLI to list failing jobs, extract error logs, classify the root cause, reproduce it locally, apply a minimal fix, and push the change with a conventional commit.

How to diagnose why a pull request check is failing?▼

Run gh pr checks on the PR URL to list failing checks, then pull per-step logs with gh run view --log-failed. Each failure is classified into categories like build, lint, test, flaky, dependency, or infra to guide the fix.

What should I do when a CI failure is caused by flaky tests?▼

First re-run only the failed jobs with gh run rerun --failed-only. If the test still fails intermittently, add retry configuration, introduce waits or polling, or remove the external dependency causing non-determinism.

Can this fix CI failures caused by GitHub outages or expired secrets?▼

No. Failures classified as infrastructure or external causes, such as registry outages, rate limits, or expired service keys, are escalated to the user with a report instead of attempting code changes.

Why does my CI fail with a lockfile out of sync error?▼

This happens when committed dependencies diverge from the lockfile. The fix is running corepack pnpm install with the Node and pnpm versions matching the project configuration, then committing the updated lockfile.