fix-ci-failures

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

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill fix-ci-failures-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-ci-failures
Source: https://github.com/Tyrizx/Tyrizx/tree/main/.github/skills/fix-ci-failures
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill fix-ci-failures-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When CI checks fail on a pull request, developers waste time clicking through GitHub Actions pages to find logs, identify the failing step, and determine whether the failure is caused by their code or by flaky infrastructure. This Skill automates that entire investigation loop from the terminal. ## Core Features & Use Cases - Failed Check Discovery: Identify the PR for the current branch, list all checks, and filter to failed ones with run and job IDs. - Log Retrieval: Download failed step logs, per-job logs via the GitHub API (even while a run is in progress), and test artifacts such as terminal.log, exthost.log, and crash dumps. - Failure Classification: Distinguish real code regressions from infrastructure issues (npm registry timeouts, Electron CDN 502s, disk space, OOM) and flaky tests, then re-run failed jobs when appropriate. - Use Case: A PR shows a red check on the Linux integration tests. The Skill locates the failed job, greps the job log for the ##[error] annotation, identifies an Electron download failure as infrastructure-related, and re-runs only the failed jobs instead of changing code. ## Quick Start Ask the assistant to investigate why the CI checks are failing on the current pull request and fix the underlying cause.

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 failed CI checks on a GitHub pull request?▼

Run gh pr checks --json name,state,link,bucket to list all checks, then filter with --jq '.[] | select(.bucket == "fail")' to show only failures. The link field contains the run ID and job ID needed to fetch logs.

How do I download GitHub Actions logs for a failed job?▼

Use gh run view <RUN_ID> --job <JOB_ID> --log-failed for failed step logs once the run completes. If the run is still in progress, call gh api repos/<owner>/<repo>/actions/jobs/<JOB_ID>/logs and save the output to a file before searching.

How can I tell if a CI failure is caused by my code or is flaky?▼

Check whether the failing test relates to files your PR changed, and compare against recent main branch runs with gh run list --branch main. Network errors, OOM, disk space, and Electron download 502s indicate infrastructure issues, not code problems.

Why does gh run view --log-failed fail while the run is in progress?▼

The --log-failed flag requires the entire run to complete, not just the failed job. While other jobs are still running, use the GitHub API endpoint for per-job logs instead, which works as soon as that job finishes.

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

Run gh run rerun <RUN_ID> --failed to re-execute only the jobs that failed. This is the recommended response to infrastructure or flaky failures rather than changing code.