gh-fix-ci

Inspect failing GitHub Actions checks and logs with the gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps debug and fix failing GitHub PR checks that run in GitHub Actions, streamlining the CI/CD process and ensuring code quality.

Core Features & Use Cases

  • Inspect Checks: Uses the gh CLI to examine failing checks and their logs.
  • Summarize Failures: Identifies the root cause of failures from logs.
  • Propose Fixes: Drafts a plan to address the identified issues.
  • Use Case: When a pull request fails its CI checks, this Skill can automatically investigate the specific errors in the GitHub Actions logs, pinpoint the problematic code, and suggest a fix.

Quick Start

Use the gh-fix-ci skill to inspect failing checks for the current pull request.

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?

Debugging failing GitHub Actions checks involves inspecting the run logs via the `gh` CLI to pinpoint the root cause of the failure and propose a targeted fix plan for the pull request.

Can I use the gh CLI to automatically summarize GitHub Actions log failures?

Yes, you can use the gh CLI to automatically examine failing GitHub Actions checks, extract the relevant error contexts from the logs, and summarize the root cause for your pull request.

Do I need gh CLI authentication to investigate failing GitHub PR checks?

Yes, investigating failing GitHub PR checks requires gh CLI authentication configured with both repository and workflow scopes to access the necessary Action run logs and check details.

What is the best way to automate drafting fix plans for failing GitHub Actions runs?

The best way to automate drafting fix plans for failing GitHub Actions runs is to parse the failure logs with the gh CLI, identify the error context, and generate a targeted resolution plan.

Does this approach work for debugging external CI providers like Buildkite?

No, this approach does not work for external CI providers like Buildkite; it specifically scopes out external platforms and focuses only on debugging failing runs within GitHub Actions.