gh-fix-ci

Analyze GitHub Actions PR checks and logs to draft fix plans.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bzellman/earp-kit --skill gh-fix-ci-bzellman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/bzellman/earp-kit/tree/main/skills/system/gh-fix-ci
Command: npx skills add https://github.com/bzellman/earp-kit --skill gh-fix-ci-bzellman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Quickly diagnose and fix failing GitHub Actions PR checks by analyzing checks, logs, and run metadata to provide actionable remediation guidance.

Core Features & Use Cases

  • Inspect PR checks, fetch logs, and summarize failures to identify root causes.
  • Draft a concise fix plan and require explicit user approval before applying changes.
  • Respect external CI providers by reporting only the details URL when integration is outside scope.

Quick Start

Run the bundled script to inspect PR checks, summarize failures, and generate a fix plan.

Frequently Asked Questions about gh-fix-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix failing GitHub Actions CI checks on my pull request?

This Skill inspects failing GitHub Actions PR checks by fetching logs and run metadata to summarize root causes. It drafts a fix plan and applies changes only after explicit user approval.

Can I automatically diagnose GitHub Actions logs to find the root cause of CI failures?

Yes, diagnosing GitHub Actions logs identifies CI failure root causes by reading run metadata and summarizing failures to provide actionable remediation guidance without manual log inspection.

Does this CI debugging workflow require GitHub authentication and repo access?

Yes, this CI debugging workflow requires GitHub authentication and repo access to inspect PR checks, fetch logs, and retrieve run metadata for GitHub-hosted CI.

What happens when CI failures originate from external providers like Buildkite?

For external CI providers like Buildkite, this workflow reports only the details URL and avoids intervention, limiting automated fix plans to GitHub-hosted CI checks to respect external integration boundaries.

Does the GitHub Actions fix plan apply code changes automatically without user approval?

No, the GitHub Actions fix plan requires explicit user approval before applying any changes, ensuring you maintain control over remediation and code modifications.