gh-fix-ci

Inspect failing PR checks and fetch GitHub Actions logs to propose a fix plan.

15|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-codex-plugin --skill gh-fix-ci-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/OutlineDriven/odin-codex-plugin/tree/main/skills/gh-fix-ci
Command: npx skills add https://github.com/OutlineDriven/odin-codex-plugin --skill gh-fix-ci-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly diagnose failing GitHub PR checks, fetch actionable Actions logs, and surface a clear failure context to speed up debugging and remediation.

Core Features & Use Cases

  • Inspect PR checks via the gh CLI and retrieve relevant GitHub Actions logs for failing runs.
  • Summarize the failure context, propose a concrete fix plan, and implement after explicit user approval.
  • Scope non-GitHub Actions checks by reporting the details URL and keeping the workflow lean for external checks.

Quick Start

Run the bundled script to inspect PR checks for a repository and PR and review the generated failure summary and 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 diagnose failing GitHub PR checks and extract actionable logs?

To diagnose failing GitHub PR checks, you can inspect the PR via the gh CLI and retrieve relevant GitHub Actions logs to surface a clear failure context for debugging.

How do I generate a fix plan for failing GitHub Actions CI runs?

You can generate a fix plan for failing GitHub Actions CI runs by analyzing the extracted logs, summarizing the failure context, and proposing a concrete remediation plan for explicit user approval.

How does this approach handle non-GitHub Actions checks during PR debugging?

For non-GitHub Actions checks during PR debugging, the workflow scopes the process by reporting the details URL and keeping the workflow lean rather than fetching external logs.

Do I need gh authentication to analyze PR CI failures?

Yes, gh authentication is required to analyze PR CI failures, as the bundled script relies on the gh CLI to inspect repository checks and fetch GitHub Actions logs.

What is the best way to automate debugging for failing CI pipelines?

The best way to automate debugging for failing CI pipelines is running a bundled script to identify failing PR checks, fetch logs, and generate a concise failure summary with a proposed fix plan.

Can I automatically implement fixes after diagnosing GitHub Actions failures?

You cannot automatically implement fixes without explicit user approval; the workflow generates a fix plan based on GitHub Actions logs and implements the changes only after you approve.