gh-fix-ci

Diagnose failing GitHub Actions checks and extract failure snippets from logs.

28|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/ma08/botfiles --skill gh-fix-ci-ma08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/ma08/botfiles/tree/main/codex/skills/gh-fix-ci
Command: npx skills add https://github.com/ma08/botfiles --skill gh-fix-ci-ma08

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious manual work of sifting through GitHub Actions logs to diagnose failing pull request checks, reducing debugging time from hours to minutes for software engineering teams.

Core Features & Use Cases

  • Automated Check Inspection: Uses the GitHub CLI to fetch failing PR check metadata and logs, with built-in fallbacks for GitHub API field drift and pending log states.
  • Targeted Failure Snippet Extraction: Pulls the most relevant error context from full run and job logs, so you don't have to parse thousands of lines of output.
  • Safe Fix Implementation: Generates a fix plan and only applies changes after you give explicit approval, with support for reporting external check details (like Buildkite) without attempting to debug out-of-scope providers.
  • Use Case: When your PR fails a test workflow, use this Skill to instantly pull the exact error snippet, get a proposed fix plan, and implement the fix only after you review and approve the changes.

Quick Start

Use the gh-fix-ci skill to inspect the failing checks on your current branch's pull request, summarize the root cause of the failures, and propose a fix plan for your approval.

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 without reading full logs?

Debug failing GitHub Actions checks by automating the extraction of run metadata and targeted failure snippets from logs. This fetches the most relevant error context directly, eliminating the need to manually parse thousands of lines of output to find the root cause.

Do I need the GitHub CLI to automate diagnosing failing CI checks?

Yes, you need authenticated GitHub CLI access with repository and workflow scopes to diagnose failing CI checks. The CLI is used to fetch failing PR check metadata and pull relevant error snippets directly from the logs.

Can I automatically apply code fixes after a GitHub Actions workflow fails?

You cannot automatically apply code fixes without explicit approval. The tool generates a fix plan based on the extracted error context and only applies changes after you review and explicitly approve them, ensuring safe implementation.

What happens if GitHub API fields drift or logs are pending when extracting CI failures?

Built-in fallbacks handle GitHub API field drift and pending log states when extracting CI failures. This ensures the tool can still fetch run metadata and pull relevant error snippets even if the API response structure changes or logs are not yet fully available.

Can this tool debug external CI providers like Buildkite failing on my PR?

It can report external check details like Buildkite without attempting to debug out-of-scope providers. The automated diagnosis and fix plan generation are scoped specifically to GitHub Actions checks on pull requests.