gh-fix-ci

Inspect failing GitHub PR CI checks and propose a fix plan.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill gh-fix-ci-jasonmichaelbell78-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/gh-fix-ci
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill gh-fix-ci-jasonmichaelbell78-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Inspect GitHub PR CI checks, fetch failing GitHub Actions logs, summarize failure context, and propose a remediation plan that can be implemented after user approval.

Core Features & Use Cases

  • Inspect PR checks and fetch GitHub Actions logs for failing workflows.
  • Summarize failure context and propose a fix plan that can be reviewed and approved before applying changes.
  • Use case: When a PR CI run fails, the skill identifies the failing step, provides relevant logs, and suggests deterministic changes to stabilize the pipeline.

Quick Start

Run the bundled Python script to fetch failing PR checks and GitHub Actions logs for a specific PR and generate a concise failure summary.

Frequently Asked Questions about gh-fix-ci

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

FAQPage Schema
How do I automatically debug and fix failing GitHub Actions CI checks on a pull request?

To automatically debug failing GitHub Actions CI checks, you need a tool that fetches failing workflow logs, summarizes the failure context, and proposes a remediation plan you can approve before changes are applied.

What is the best way to summarize GitHub Actions PR failures before applying code fixes?

Summarizing GitHub Actions PR failures is done by inspecting PR checks and extracting relevant logs to identify the failing step, which then allows a deterministic fix plan to be generated for review.

Do I need GitHub CLI authentication to analyze failing PR CI workflows?

Yes, GitHub CLI authentication is required to analyze failing PR CI workflows, because the inspection script relies on it to securely fetch pull request checks and GitHub Actions logs.

Can I review a CI failure fix plan before the code changes are implemented?

Yes, you can review a CI failure fix plan before implementation, because the workflow enforces a plan-based approval process where it summarizes failure context and waits for your approval to apply changes.

Does this automated debugging approach work with all pull request checks on GitHub?

This automated debugging approach applies specifically to pull requests with failing CI on GitHub Actions, fetching workflow logs and proposing fixes for the identified failing steps.

Why does my GitHub Actions CI fix require approval before stabilizing the pipeline?

Your GitHub Actions CI fix requires approval to ensure deterministic changes are reviewed before implementation, preventing unintended modifications while stabilizing the pipeline after a failure.