gh-fix-ci

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

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill gh-fix-ci-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/plugins/cache/openai-curated/github/27651a43bf55185d924f7a1fc49043a0a8be65a0/skills/gh-fix-ci
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill gh-fix-ci-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Failing pull request checks in GitHub Actions require manually digging through run pages and logs to find the root cause. This Skill automates that inspection: it resolves the PR, identifies failing checks, pulls the relevant GitHub Actions logs, and extracts a focused failure snippet so you can diagnose and fix the issue faster. ## Core Features & Use Cases - Automated Check Inspection: Runs gh pr checks with field-drift fallbacks to list failing checks for a PR number, URL, or the current branch. - Log Retrieval and Snippet Extraction: Fetches run logs via gh run view --log, falls back to per-job logs through the GitHub API when runs are still in progress, and extracts a failure-centered snippet. - Structured Output for Automation: Emits JSON with --json and exits non-zero while failures remain, so it can gate CI-fix automation loops. - Use Case: A PR shows three red checks. Run the bundled script to get each failing check's name, run URL, and a concise error snippet, then propose a focused fix plan before touching any code. ## Quick Start Ask the assistant to use the gh-fix-ci skill to inspect the failing GitHub Actions checks on the current pull request, summarize the root cause, and propose the smallest viable 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 find why a GitHub Actions check failed on my PR?▼

Run the bundled inspect_pr_checks.py script with your PR number or URL. It lists failing checks via gh pr checks, fetches the Actions run logs, and prints a failure-centered log snippet with the run URL for each failing check.

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

Use gh run view <run_id> --log after extracting the run id from the check's detailsUrl. If the run is still in progress, the script falls back to gh api /repos/<owner>/<repo>/actions/jobs/<job_id>/logs for the specific job.

Does this work with Buildkite or other non-GitHub CI providers?▼

No. Checks whose detailsUrl does not point to a GitHub Actions run are labeled external and only reported with their URL. The workflow intentionally does not attempt Buildkite or other providers.

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

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

Why does the script report log_pending for a failing check?▼

GitHub does not publish run logs until the run completes. When the log response indicates the run is still in progress, the script marks the check as log_pending and suggests retrying once the run finishes.

Can I use the check inspection output in automation?▼

Yes. Pass --json to get machine-friendly output containing the PR, each failing check, run metadata, and log snippets. The script exits non-zero while failures remain, so it can gate automated fix loops.