# Gh Fix CI

> Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Verify gh authentication, inspect failing checks and logs, summarize the root failure, propose a focused fix plan, and implement only after explicit user approval.

- Skill: `jlnbuiles/gh-fix-ci` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add jlnbuiles/gh-fix-ci`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jlnbuiles/gh-fix-ci/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: jlnbuiles (https://skillmd.com/u/jlnbuiles)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/jlnbuiles/gh-fix-ci

---


# GitHub Fix CI

Use this skill for failing GitHub Actions checks on a PR.

Run all `gh` commands with elevated network access.

## Expert Standard

- Think like a senior engineer debugging CI under time pressure.
- Give advice like an expert: identify the real root cause, not just the loudest error.
- Execute like an expert: reproduce the smallest useful failure, make the narrowest correct fix, and validate it.

## Communication Style

- Explain failures in plain English.
- Turn each broken check into a simple story: what failed, why it failed, and what fixes it.
- Keep summaries short and practical.
- Avoid dumping raw logs when one or two clear lines explain the issue.

## Scope

- In scope: GitHub Actions checks reachable through `gh`
- Out of scope: external CI providers; report the details URL only

## Workflow

1. Run `gh auth status`. If unauthenticated, stop and ask the user to run `gh auth login`.
2. Resolve the PR from the current branch unless the user provides one.
3. Inspect failing checks with:
   `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"`
4. Summarize each failure with:
   - check name
   - failed step or strongest failure line
   - likely root cause
   - failure type: deterministic, flaky, environmental, or external
   - run URL
5. Propose a short fix plan and ask for approval.
6. After approval, make the smallest coherent fix and run the most relevant validation.
7. Summarize the diff, residual risk, and whether the checks should be re-run.

## Rules

- Collapse multiple failing checks into one remediation path when they share a root cause.
- If the failure is flaky or external, say so instead of forcing a speculative code change.
- Use manual `gh` commands only if the bundled script is insufficient.
- Keep the debugging expert-grade, but make the explanation understandable to a non-specialist.