gh-fix-ci

Inspect failing GitHub PR checks and extract GitHub Actions failure logs for fix planning.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill gh-fix-ci-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28tooling%29/gh-fix-ci
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill gh-fix-ci-peterson-benhame

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 error-prone. This Skill automates locating failing checks, fetching their logs, and summarizing the failure context so you can plan and apply a fix with explicit approval. ## Core Features & Use Cases - Automated Check Inspection: Uses the GitHub CLI (gh) to list PR checks, identify failures, and extract run and job IDs from details URLs. - Log Retrieval with Fallbacks: Fetches run logs via gh run view --log and falls back to the job logs API when runs are still in progress, then extracts a focused failure snippet. - Approval-Gated Fixes: Summarizes failures, drafts a fix plan (optionally via a create-plan skill), and only implements changes after explicit user approval. - Use Case: A PR shows three failing checks. Run the bundled script to get each failing check's name, run URL, and a concise error snippet, then approve a plan to fix the root cause and re-run gh pr checks to confirm. ## Quick Start Ask the agent to inspect the failing checks on the current pull request 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 PR checks with the gh CLI?

Run the bundled inspect_pr_checks.py script with your PR number or URL to list failing checks and pull their GitHub Actions logs. It extracts run IDs from details URLs, fetches logs, and prints a focused failure snippet for each check.

How to fetch GitHub Actions logs for a failed workflow run?

Use gh run view <run_id> --log to retrieve the full run log. If the run is still in progress, the script falls back to the gh api endpoint for individual job logs using the job ID parsed from the check URL.

Does this work with Buildkite or other CI providers?

No, external CI providers are explicitly out of scope. When a check's details URL is not a GitHub Actions run, the skill labels it as external and only reports the URL without attempting log retrieval.

What authentication is required for gh pr checks inspection?

You need the GitHub CLI installed and authenticated via gh auth login with repo and workflow scopes. The script verifies authentication with gh auth status and exits with an error if gh is missing or unauthenticated.

Why does the script report logs as pending or unavailable?

Logs are marked pending when GitHub reports the run is still in progress, and unavailable when log retrieval fails entirely. In both cases the script reports the check metadata and error message instead of a failure snippet.

Can this skill fix PR review comments as well?

No, addressing PR review comments is explicitly out of scope and handled by a separate skill such as gh-address-comments. This skill focuses only on failing GitHub Actions checks and implements fixes only after explicit user approval.