gh-fix-ci

Inspect GitHub PR check statuses and propose fixes via the gh CLI.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill gh-fix-ci-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/gh-fix-ci
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill gh-fix-ci-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps debug and fix failing GitHub Pull Request checks that are running in GitHub Actions, streamlining the CI/CD pipeline and ensuring code quality.

Core Features & Use Cases

  • Inspect Checks: Uses the gh CLI to examine the status and details of GitHub PR checks.
  • Summarize Failures: Extracts relevant log snippets from failing GitHub Actions to pinpoint the root cause.
  • Propose Fixes: Drafts a plan to address the identified issues and implements it after user approval.
  • Use Case: When a pull request fails its CI checks, this Skill can automatically fetch the logs, identify the specific error message, and suggest a code change to fix it.

Quick Start

Use the gh-fix-ci skill to inspect the 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?

To debug failing GitHub Actions checks, you can use a Skill that inspects PR check statuses via the `gh` CLI, extracts actionable log snippets, and summarizes failure contexts to pinpoint root causes.

Can I automatically fix failing CI/CD checks in GitHub Actions?

Yes, you can automatically fix failing CI/CD checks by summarizing GitHub Actions logs and proposing code changes, which are implemented only after receiving explicit user approval.

Do I need `gh` CLI authentication to inspect GitHub PR check statuses?

Yes, inspecting GitHub PR check statuses requires `gh` CLI authentication configured with both repository and workflow scopes to fetch actionable logs and failure contexts.

What is the best way to find the root cause of a failed GitHub Actions workflow?

The best way to find the root cause of a failed GitHub Actions workflow is to fetch relevant log snippets from failing checks, which extracts and summarizes the specific error context for you.

How does this approach propose fixes for failing pull request checks?

This approach proposes fixes for failing pull request checks by drafting a plan to address identified issues from GitHub Actions logs, implementing the code changes after you explicitly approve them.