gh-fix-ci

Inspect failing GitHub Actions PR checks and summarize actionable log snippets.

1|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/TMYTiMidlY/skills --skill gh-fix-ci-tmytimidly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/TMYTiMidlY/skills/tree/main/skills/.experimental/gh-fix-ci
Command: npx skills add https://github.com/TMYTiMidlY/skills --skill gh-fix-ci-tmytimidly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the triage of failing GitHub Actions workflows so users stop juggling multiple logs, URLs, and failure summaries when a pull request check goes red.

Core Features & Use Cases

  • Automated Failure Detection: Runs gh pr checks (with adaptive field fallbacks) and the bundled inspect_pr_checks.py script to locate failing jobs and capture their metadata.
  • Log Retrieval & Highlighting: Streams workflow and job logs, handles pending runs, notes external providers, and extracts concise failure snippets plus tail context.
  • Review Workflow Integration: Guides the user through verifying gh authentication, drafting a concise plan (via create-plan when available), implementing the approved fix, and re-running checks before reporting.

Quick Start

Run python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123" to gather failing check logs and summarize root causes.

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 the root cause of failing GitHub Actions PR checks?

To find the root cause of failing GitHub Actions PR checks, this Skill runs the bundled inspect_pr_checks.py script to fetch run metadata, stream workflow logs, and extract concise failure snippets with tail context for actionable triage.

What is the best way to triage pending or failed GitHub Actions workflows?

Triage of failed or pending GitHub Actions workflows is handled by streaming job logs, noting external providers, and applying adaptive field fallbacks via the gh pr checks command to locate failing jobs and capture their metadata.

Do I need GitHub CLI authentication to debug CI logs with this tool?

Yes, you need authenticated GitHub CLI access to debug CI logs, as the Skill requires gh CLI to run pr checks and fetch metadata, logs, and failure markers for the current branch or a user-provided PR number.

How do I get actionable log snippets from a failing CI pull request?

You get actionable log snippets from a failing CI pull request by running python inspect_pr_checks.py with the repository and PR number, which streams workflow logs and highlights concise failure markers plus tail context.

Can I use this to triage GitHub Actions checks for a specific PR URL?

Yes, you can triage GitHub Actions checks by providing a specific PR URL or PR number, which the Skill parses to fetch failing job metadata and summarize log snippets for the targeted pull request.

What should I do after extracting failure snippets from GitHub Actions logs?

After extracting failure snippets from GitHub Actions logs, you should verify gh authentication, draft a concise fix plan, implement the approved changes, and re-run the checks before reporting the results.