gh-fix-ci

Identify failing GitHub Actions checks and propose a remediation plan with approval step.

Updated Dec 27, 2018
One-click install
npx skills add https://github.com/segersniels/dotfiles --skill gh-fix-ci-segersniels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/segersniels/dotfiles/tree/main/.codex/skills/gh-fix-ci
Command: npx skills add https://github.com/segersniels/dotfiles --skill gh-fix-ci-segersniels

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the detection and explanation of failing GitHub Actions checks on pull requests, surfacing actionable logs and failure context.

Core Features & Use Cases

  • Locate failing checks via the GitHub CLI and PR data.
  • Retrieve and summarize GitHub Actions logs to highlight root causes.
  • Draft a concise fix plan and require explicit approval before applying changes.
  • Re-scan checks after changes to verify success and notify stakeholders.

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 fix failing GitHub Actions checks on a pull request?

To fix failing GitHub Actions checks, you can run the bundled script to automatically locate failing PR checks, pull actionable logs, and generate a failure report highlighting root causes. It then drafts a fix plan and requires explicit approval before applying changes.

Can I retrieve GitHub Actions logs for my current branch without a PR number?

Yes, you can retrieve GitHub Actions logs for your current branch. The script supports identifying failing checks using both direct pull request numbers and your current active branch, pulling the relevant run metadata and failure context via the GitHub CLI.

Do I need the GitHub CLI installed to analyze failing PR checks?

Yes, you need the GitHub CLI (gh) installed and authenticated to analyze failing PR checks. The script relies on gh to fetch check statuses, retrieve GitHub Actions logs, and pull run metadata for the target pull request.

How does this workflow ensure safety before applying changes to fix CI failures?

The workflow ensures safety by drafting a concise fix plan and prompting for explicit approval before implementing any changes. After changes are applied, it re-scans checks to verify success and notifies stakeholders of the updated status.

What is the best way to summarize GitHub Actions failure context for a PR?

The best way to summarize GitHub Actions failure context is to use a dedicated script that retrieves logs and run metadata via gh. It surfaces actionable failure context and highlights root causes to guide you through a structured fix plan.