gh-fix-ci

Diagnoses and fixes failing GitHub PR checks by locating erroneous workflows and extracting failure logs.

3|Updated Jan 14, 2022

Search Tags:#automation #debugging #logs #github #ci #gh-cli #pr-checks

Ready to run

npx skills add https://github.com/bingran-you/bingran-you --skill gh-fix-ci-bingran-you

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/bingran-you/bingran-you/tree/main/repo-skills/gh-fix-ci
Command: npx skills add https://github.com/bingran-you/bingran-you --skill gh-fix-ci-bingran-you

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps engineers quickly diagnose and fix failing GitHub PR checks by locating failing workflows, collecting actionable logs, summarizing failure context, and drafting a fix plan that requires explicit approval before implementing changes.

Core Features & Use Cases

Inspect PR checks and fetch GitHub Actions logs to extract failure snippets.
Generate a concise, contextual fix plan and require approval before making changes.
Maintain a lean workflow by focusing on GitHub Actions and reporting only the details URL for external checks.

Quick Start

Run the bundled script to inspect PR checks and generate a failure report.

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 and fix failing GitHub Actions PR checks?▼

To debug failing GitHub Actions PR checks, you analyze workflow logs, extract failure snippets, and generate a corrective fix plan that requires explicit approval before implementation. This approach targets GitHub Actions-based pipelines to resolve CI failures efficiently.

What is the best way to extract failure snippets from GitHub Actions logs?▼

Extracting failure snippets from GitHub Actions logs involves fetching PR checks via gh CLI, isolating actionable error context, and summarizing the failure details. This generates a targeted fix plan gated behind user consent to ensure accurate corrections.

Do I need gh CLI authentication to diagnose GitHub PR check failures?▼

Yes, gh CLI authentication is required to diagnose GitHub PR check failures. The diagnostic process requires authenticated gh CLI access to fetch PR checks, collect actionable logs, and propose corrective changes for failing GitHub Actions workflows.

Can I use this approach for external CI checks outside of GitHub Actions?▼

For external CI checks outside of GitHub Actions, this approach maintains a lean workflow by reporting only the details URL. It specifically applies to GitHub Actions-based PR pipelines for log analysis, failure snippet extraction, and plan-driven implementation.

How do I ensure code changes are gated behind user consent when fixing CI failures?▼

To ensure code changes are gated behind user consent when fixing CI failures, the workflow uses optional plan integration requiring explicit approval before implementing changes. This plan-driven implementation guarantees corrective changes are applied only after user consent.