gh-fix-ci

Diagnose failing GitHub Actions PR checks and draft actionable fix plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This capability helps engineers diagnose and fix failing GitHub Actions PR checks by using gh to inspect checks, summarize failure context, draft a fix plan, and implement only after explicit approval. It excludes external providers (for example Buildkite) and reports only the details URL when relevant.

Core Features & Use Cases

  • Inspect failing PR checks and fetch actionable GitHub Actions logs.
  • Summarize failure context and draft a concise fix plan for approval.
  • Scope the workflow to GitHub Actions and related PR workflows; report only the details URL when external providers are involved.

Quick Start

Use the included script to inspect PR checks and summarize failures, then draft and approve a fix plan before implementing changes.

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?

To debug failing GitHub Actions checks, you can inspect PR checks, parse run and job IDs from the details URL, fetch run metadata and logs via the GitHub CLI, and generate an actionable failure snippet with a fix plan.

Can I use this to diagnose CI failures from external providers like Buildkite?

No, diagnosing CI failures is scoped strictly to GitHub Actions workflows and PR checks. For external CI providers like Buildkite, it only reports the details URL without parsing logs or generating a fix plan.

How do I get actionable remediation steps from GitHub Actions logs?

Getting actionable remediation steps involves reading failing PR checks, fetching run metadata and logs through GitHub CLI, summarizing the failure context, and drafting a concise plan for approval before implementing changes.

Do I need GitHub CLI authentication to read PR check logs?

Yes, GitHub CLI authentication is required to read PR check logs. The process depends on gh authentication to fetch run metadata, retrieve logs, and produce failure snippets for diagnosis.

What is the best way to fix GitHub Actions PR check failures automatically?

The best way to fix GitHub Actions PR check failures is to summarize failure context, draft a plan-based fix for explicit approval, and only implement changes after receiving confirmation to ensure controlled remediation.

Why does my GitHub Actions fix plan require explicit approval before implementation?

Explicit approval is required before implementation to ensure controlled remediation of GitHub Actions failures. The workflow summarizes logs and drafts the fix plan first, preventing unreviewed automated changes to your repository.