fix-ci-failures

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

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

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 structured workflow to locate failed checks, download the right logs or artifacts, pinpoint 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. - Log Retrieval Strategies: View failed step logs directly, download test 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 (network timeouts, disk space, Electron download failures) and flaky tests, then re-run failed jobs when appropriate. - Use Case: A PR shows a failing Linux integration test. Use this Skill to download the job log, grep for the ##[error] annotation, read the surrounding context, determine whether the failure relates to your changes, fix it, push, and watch the checks turn green. ## Quick Start 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 patterns like 'error TS' or 'AssertionError' to locate the root cause.

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 job 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 finish, but the GitHub API endpoint for job logs works as soon as the individual job completes. Download it with gh api and search for the ##[error] annotation.

How do I tell if a CI failure is caused by my PR or is flaky?▼

Check whether the failing test relates to code you changed, look for infrastructure signatures like ETIMEDOUT, ENOMEM, or Electron download errors, and compare against recent main branch runs with gh run list. Re-run failed jobs with gh run rerun --failed for suspected flakes.

What tools are required to debug GitHub CI failures from the terminal?▼

You need the GitHub CLI (gh) authenticated to the repository, plus git for branch and commit operations. Standard Unix tools like grep, sed, and tail are used to search large log files for error annotations.