resolve-ci-failures

Analyzes failing GitHub CI checks, fetches failure logs, and delegates root-cause fixes.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/fx/skills --skill resolve-ci-failures-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-ci-failures
Source: https://github.com/fx/skills/tree/main/skills/resolve-ci-failures
Command: npx skills add https://github.com/fx/skills --skill resolve-ci-failures-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When pull request checks go red, developers must manually dig through GitHub Actions logs, categorize each failure, and coordinate fixes — a slow, error-prone process. This Skill automates that triage: it detects failing checks, fetches logs and annotations, classifies each failure, and delegates fixes while enforcing rules like never skipping tests. ## Core Features & Use Cases - Failure Detection & Log Retrieval: Queries PR check runs via the GitHub CLI, fetches annotations and workflow job logs, and detects base-branch merge conflicts that silently block CI from running. - Failure Categorization: Classifies each failure as test, build, lint/format, security, flaky, or infrastructure, with a defined action per category. - Delegated Fixing with Guardrails: Delegates root-cause fixes to the coder skill, batches all fixes into a single push, and forbids test skipping or lint suppression. - Use Case: After pushing code to a PR, the tests and lint checks fail. Invoke this Skill to fetch the failure logs, fix the assertion error and formatting issues, push once, and report a summary table of resolutions. ## Quick Start Resolve the failing CI checks on my current pull request and push the fixes.

Frequently Asked Questions about resolve-ci-failures

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

FAQPage Schema
How do I fix failing CI checks on a GitHub pull request?▼

Use gh pr checks to list failed checks, fetch logs with gh run view --log-failed or the check-runs API, then categorize each failure and fix the root cause. This Skill automates that flow and delegates fixes to a coder sub-agent.

Why is CI not running on my GitHub pull request?▼

GitHub Actions does not trigger CI on PRs with merge conflicts against the base branch. Check gh pr view for mergeable: CONFLICTING, then rebase onto the base branch and force-push to unblock CI.

How do I get logs for a failed GitHub Actions check?▼

Run gh run view RUN_ID --log-failed for failed step output, or query the check-runs API for annotations. If output is too large, fetch individual job logs via the actions/jobs API endpoint.

Can I skip a failing test to make CI pass?▼

No. This Skill explicitly forbids test.skip, it.skip, describe.skip, and unjustified lint suppression. Fixes must address root causes, and infrastructure failures are reported to the user rather than patched.

What types of CI failures can be fixed automatically?▼

Test failures, build errors, lint/format issues, and security scan findings are delegated to the coder skill for fixes. Flaky tests are noted for re-run, and infrastructure failures like runner timeouts are reported, not fixed.