Github: Fix CI

Diagnose failing GitHub Actions checks and propose a repair plan.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/davidkelley/searchlite --skill github-fix-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Github: Fix CI
Source: https://github.com/davidkelley/searchlite/tree/main/.codex/skills/gh-fix-ci/scripts
Command: npx skills add https://github.com/davidkelley/searchlite --skill github-fix-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnose failing GitHub Actions checks by pulling actionable logs.

Core Features & Use Cases

  • Inspect PR checks with gh to identify failing workflows.
  • Fetch and summarize GitHub Actions logs to provide a failure context.
  • Create a fix plan and implement changes after user approval.

Quick Start

Use the gh-fix-ci skill to inspect PR checks and fetch actionable logs.

  • python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"
  • Add --json for machine-friendly output.

Frequently Asked Questions about Github: Fix CI

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

FAQPage Schema
How do I diagnose failing GitHub Actions checks from PR logs?

To diagnose failing GitHub Actions checks, you can pull and summarize actionable logs from specific PR runs to identify the failing workflows and extract the failure context. This summarizes the logs to provide a clear failure context.

Can I automatically generate a repair plan for a failing GitHub CI workflow?

Yes, you can automatically generate a repair plan for a failing GitHub CI workflow by inspecting PR checks, summarizing the extracted job logs, and proposing a concise implementation plan for your approval.

Do I need the gh CLI installed to inspect GitHub Actions logs?

Yes, you need the gh CLI installed to authenticate with GitHub, inspect PR checks, and fetch run and job logs for diagnosing CI failures. The tool relies on gh to extract the necessary actionable logs.

What is the best way to extract machine-friendly output from GitHub CI logs?

The best way to extract machine-friendly output from GitHub CI logs is to run the inspection script with the --json flag, which formats the summarized PR checks and failure context for automated processing.

How do I get a summarized failure context from GitHub Actions run logs?

You get a summarized failure context from GitHub Actions run logs by executing a script that authenticates with gh, inspects the specific PR checks, and formats the extracted job logs into a concise actionable summary.