fix-ci-failures

Diagnose and fix failing CI checks on GitHub pull requests using the gh CLI.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/voidful/Aixlarity --skill fix-ci-failures-voidful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-ci-failures
Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/.github/skills/fix-ci-failures
Command: npx skills add https://github.com/voidful/Aixlarity --skill fix-ci-failures-voidful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When CI checks fail on a pull request, finding the actual cause means digging through GitHub Actions runs, job logs, and artifacts. This Skill provides a structured workflow to locate failed checks, download the right logs, extract the real error, and determine whether the failure is caused by your code or by infrastructure flakiness. ## Core Features & Use Cases - Failed Check Discovery: Identify the PR for the current branch, list all checks, and filter to failed ones with gh pr checks. - Log Retrieval Strategies: View failed step logs directly, download log and crash-dump artifacts, or fetch per-job logs via the GitHub API while a run is still in progress. - Failure Classification: Distinguish code-caused failures from infrastructure issues (npm registry errors, Electron CDN failures, disk space, timeouts) and flaky tests, with guidance to re-run jobs instead of changing code. - Use Case: A PR shows a failing "Linux / Electron" integration test. Use this Skill to download the logs-linux-x64-electron-1 artifact, inspect exthost.log for the assertion failure, fix the code, push, and watch the checks turn green. ## Quick Start Find the failing CI checks on my current pull request, download the logs, tell me the root cause, and help me fix it.

Frequently Asked Questions about fix-ci-failures

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

FAQPage Schema
How do I find why a GitHub Actions CI check failed on my PR?

Run `gh pr checks --json name,state,link,bucket` to list failed checks, extract the run ID from the check link, then use `gh run view <RUN_ID> --job <JOB_ID> --log-failed` to see the failed step output. Grep for `##[error]` to jump to the exact failure line.

How to download GitHub Actions job logs while a run is still in progress?

Use the GitHub API: `gh api repos/<owner>/<repo>/actions/jobs/<JOB_ID>/logs > log.txt`. This works for completed jobs even when the overall run is still running, unlike `--log-failed` which requires the entire run to finish.

How do I know if a CI failure is caused by my code or is a flaky test?

Check whether the failing test relates to code you changed, and compare against recent main branch runs with `gh run list --branch main`. Infrastructure signs like npm network errors, ENOMEM, or Electron download 502s indicate the failure is not your code.

Can I re-run only the failed jobs in a GitHub Actions workflow?

Yes, run `gh run rerun <RUN_ID> --failed` to re-execute only the failed jobs. This is the recommended action for infrastructure failures and flakes instead of changing code.

What tools are required to debug CI failures with this workflow?

The GitHub CLI (`gh`) is required for all operations: viewing PR checks, inspecting runs, downloading artifacts, and calling the API. Standard Unix tools like grep, sed, and tail are used to search large log files.