gh-fix-ci

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

1|Updated May 25, 2020
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill gh-fix-ci-titaneric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/gh-fix-ci
Command: npx skills add https://github.com/titaneric/dotfiles --skill gh-fix-ci-titaneric

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 locating failing checks, fetching their logs, and summarizing the failure context so you can move straight to planning a fix. ## Core Features & Use Cases - Automated Check Inspection: Uses the GitHub CLI to list failing PR checks, resolve run and job IDs, and pull GitHub Actions logs with fallbacks for pending or unavailable logs. - Failure Snippet Extraction: Scans logs for error markers and extracts a focused snippet around the failure for quick diagnosis. - Plan-Before-Fix Workflow: Summarizes failures, drafts a fix plan, and only implements changes after explicit user approval. - Use Case: A PR shows red checks before merge. Run the bundled script to instantly see which GitHub Actions jobs failed, view the relevant log excerpts, and get an approved fix plan without opening the browser. ## Quick Start Ask the assistant to inspect the failing checks on the current pull request, summarize the root cause, 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 gh, and prints a focused failure snippet for each failing check.

How to get GitHub Actions logs from the command line?

Use gh run view <run_id> --log to fetch run logs, or gh api /repos/<owner>/<repo>/actions/jobs/<job_id>/logs for individual job logs. The script automates 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. Checks whose details URL is not a GitHub Actions run are labeled external, and only the URL is reported without attempting to fetch logs.

Why does the script say gh is not authenticated?

The GitHub CLI must be authenticated before inspecting checks. Run gh auth login with repo and workflow scopes, then verify with gh auth status before rerunning the script.

What happens when GitHub Actions logs are still in progress?

When run logs report they are still in progress, the script falls back to fetching job logs directly via the GitHub API. If logs remain unavailable, it marks the check as log_pending and reports the note instead of failing silently.