fix-ci

Name: fix-ci
Availability: InStock
Author: paulbrittain

Fix failing GitHub PR checks by applying minimal safe changes.

Updated May 22, 2026

Search Tags:#automation #debugging #pull request #github actions #build failures #ci

Ready to run

npx skills add https://github.com/paulbrittain/claude-team-kit --skill fix-ci-paulbrittain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-ci
Source: https://github.com/paulbrittain/claude-team-kit/tree/main/skills/fix-ci
Command: npx skills add https://github.com/paulbrittain/claude-team-kit --skill fix-ci-paulbrittain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of failing CI checks that block a pull request, by helping you quickly identify the root cause and apply the smallest safe fix.

Core Features & Use Cases

CI failure triage: Pulls the failing job details from gh pr checks (and uses logs or the check link when needed) to extract the first actionable error.
Focused iterative repair: Applies one minimal, low-risk fix at a time, then re-checks the PR until the checks are green.
Clear accountability: Produces an ordered record of what failed, what was changed, and what the next action is based on the current CI state.

Quick Start

Run the skill while your PR is failing and ask it to find the first actionable CI failure, apply the smallest safe fix, and iterate until all checks pass.

Frequently Asked Questions about fix-ci

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

FAQPage Schema

How do I fix failing GitHub Actions checks on a pull request?▼

Use `gh pr checks` to pull the failing job details, extract the first actionable error from the logs, apply the smallest safe fix to your pull request, and iterate with re-checks until the GitHub Actions checks pass.

What is the best way to debug CI build failures blocking a pull request?▼

The best way to debug CI build failures is to locate the first actionable error in the failed job logs, apply one low-risk minimal change at a time, and re-check the PR until the checks are green.

Does this approach work with GitHub Actions check sets that only provide a check link?▼

Yes, this approach works with GitHub Actions check sets by using `gh pr checks` as the source of truth and utilizing the provided logs or check links to identify the failing command or service.

How do I locate the root cause of a failed GitHub Actions job?▼

You locate the root cause of a failed GitHub Actions job by extracting the first actionable error from the failed job logs or check link, rather than manually reviewing the entire build output.

Why should I apply only minimal fixes when resolving CI build failures?▼

Applying minimal fixes when resolving CI build failures ensures you make one low-risk change at a time, maintaining clear accountability of what was changed while safely iterating towards a green PR.

When should I not use an automated iterative repair approach for CI failures?▼

You should avoid automated iterative repair for CI failures if your GitHub Actions workflows do not rely on standard check sets or if `gh pr checks` cannot access the logs needed to identify the failing command.