gh-fix-ci

Inspect failing GitHub Actions PR checks and extract failure log snippets with gh CLI.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill gh-fix-ci-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/AarnavBaddam/skills/tree/main/gh-fix-ci
Command: npx skills add https://github.com/AarnavBaddam/skills --skill gh-fix-ci-aarnavbaddam

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 runs and logs, which is slow and error-prone. This Skill automates the inspection of failing PR checks, pulls the relevant logs, and surfaces the root cause so you can propose and apply a focused fix. ## Core Features & Use Cases - Automated Check Inspection: Runs gh pr checks and the bundled script to identify failing GitHub Actions checks, handling gh field drift and log fallbacks automatically. - Failure Snippet Extraction: Fetches run and job logs, then extracts a concise failure snippet around error markers for fast root-cause analysis. - Guided Fix Workflow: Summarizes the root cause, proposes a focused fix plan, and implements changes only after explicit user approval. - Use Case: A PR shows red checks before merge. Run the inspection script to get each failing check's run URL and log snippet, confirm the root cause, then apply and verify the approved fix locally. ## Quick Start Ask the assistant to use gh-fix-ci to inspect the failing GitHub Actions checks on the current PR, summarize the root cause, and propose a fix.

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 run logs via gh, and extracts a failure snippet so you can identify the root cause before proposing a fix.

How to get GitHub Actions logs for a failed PR check using gh CLI?

Extract the run id from the check's detailsUrl, then run gh run view <run_id> --log. If the run is still in progress, fetch job logs directly with gh api /repos/<owner>/<repo>/actions/jobs/<job_id>/logs.

Does this workflow support Buildkite or other CI providers?

No. Checks whose detailsUrl is not a GitHub Actions run are labeled external and only reported with their URL. Buildkite and other providers are out of scope unless the user explicitly requests a separate investigation.

Why does gh pr checks fail with unknown JSON fields?

The gh CLI occasionally changes available fields for pr checks. The script detects the rejected fields, parses the available fields reported by gh, and retries with a supported subset automatically.

What authentication is required to inspect GitHub Actions logs?

You need the GitHub CLI installed and authenticated via gh auth login with repo and workflow scopes. Verify access with gh auth status before running the inspection.