gh-fix-ci

Inspect failing GitHub Actions PR checks, extract failure logs, and plan fixes.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill gh-fix-ci-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/tools/gh-fix-ci
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill gh-fix-ci-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Debugging failing pull request checks requires manually digging through GitHub Actions logs, which is slow and repetitive. This Skill automates the inspection of failing PR checks, pulls the relevant log snippets, and guides a structured fix workflow with explicit approval before any code changes. ## Core Features & Use Cases - Automated Check Inspection: Uses the GitHub CLI (gh) to list failing PR checks, resolve run and job IDs, and fetch GitHub Actions logs with fallbacks for pending or unavailable logs. - Failure Snippet Extraction: The bundled Python script scans logs for error markers and extracts a focused failure snippet plus a log tail for quick diagnosis. - Approval-Gated Fix Workflow: Summarizes failures, drafts a fix plan (optionally via a create-plan skill), and only implements changes after explicit user approval. - Use Case: A pull request shows three red checks. Run the Skill to identify which GitHub Actions jobs failed, see the exact error lines from the logs, get a proposed fix plan, and apply it after review. ## Quick Start Ask the agent to inspect the failing checks on the current pull request, summarize the root cause from the GitHub Actions logs, and propose a fix plan before making any changes.

Frequently Asked Questions about gh-fix-ci

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

FAQPage Schema
How do I debug failing GitHub Actions checks on a pull request?▼

Run the bundled inspect_pr_checks.py script with the repo path and PR number or URL. It lists failing checks, fetches GitHub Actions logs via the gh CLI, and extracts a focused failure snippet so you can see the exact error lines.

How to fetch GitHub Actions logs from the command line?▼

Use gh run view <run_id> --log to fetch full run logs, or gh api /repos/<owner>/<repo>/actions/jobs/<job_id>/logs for individual job logs. The script handles both, including fallback to job logs when run logs are still pending.

Does this work with Buildkite or other CI providers?▼

No, only GitHub Actions checks are analyzed. When a check's details URL is not a GitHub Actions run, it is labeled external and only the URL is reported without log fetching or analysis.

Why does gh pr checks fail with a field error?▼

The gh CLI occasionally changes which JSON fields are available for pr checks. The script detects the available fields listed in the error message and automatically retries with a supported field set.

What authentication is required to inspect PR checks with gh?▼

You need the GitHub CLI authenticated via gh auth login with repo and workflow scopes. Verify access by running gh auth status inside the repository before inspecting checks.