fix-ci-failures

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

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill fix-ci-failures-kevinhuangislearning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-ci-failures
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/.github/skills/fix-ci-failures
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill fix-ci-failures-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When CI checks fail on a pull request, finding the actual error means digging through thousands of lines of GitHub Actions logs. This Skill provides a systematic workflow to locate failed checks, download the right logs, extract the root cause, and iterate on a fix without guesswork. ## Core Features & Use Cases - Failed check discovery: Identify the PR for the current branch, list failed checks, and extract run and job IDs from check URLs using the gh CLI. - 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 triage: Distinguish real code regressions from infrastructure issues (npm registry errors, disk space, Electron download failures) and flaky tests, then re-run or fix accordingly. - Use Case: A PR shows a red check on the Linux integration test job. Use this Skill to pull the job log, grep for ##[error], find the assertion failure, fix the code, push, and watch the checks turn green. ## Quick Start Ask the assistant to investigate why the CI checks are failing on my current pull request and help me fix the underlying issue.

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 check failed on my PR?▼

Run gh pr checks to list failed checks, extract the run ID from the check URL, then use gh run view with --log-failed to see the failed step output. Grep for ##[error] to jump directly to the failing line.

How to download GitHub Actions logs for a failed job?▼

Use gh run view <RUN_ID> --job <JOB_ID> --log-failed for completed runs, or gh api repos/<owner>/<repo>/actions/jobs/<JOB_ID>/logs to fetch a single job's log while the run is still in progress. Save large logs to a file before searching.

Can I get CI logs while the workflow run is still in progress?▼

Yes. The --log-failed flag requires the entire run to complete, but the GitHub API endpoint for per-job logs works as soon as that individual job finishes. Download it with gh api and search the saved file locally.

How do I tell if a CI failure is caused by my code or infrastructure?▼

Check whether the failing test relates to files you changed and whether the same failure appears on recent main branch runs. Network errors, disk space issues, and runner cancellations indicate infrastructure problems that a re-run usually resolves.

How do I re-run only the failed jobs in a GitHub Actions run?▼

Run gh run rerun <RUN_ID> --failed to re-execute only the jobs that failed. This is the right response for infrastructure failures and flaky tests where no code change is needed.