gh-fix-ci

Inspect failing GitHub PR checks and propose fixes using the gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and 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 the status and details of GitHub PR checks.
  • Summarize Failures: Fetches and analyzes logs 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 investigate the logs, identify the specific error, 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 PR checks automatically?

You can debug failing GitHub Actions PR checks by using this Skill to fetch detailed workflow logs via the gh CLI, summarize the failure context, and propose a code fix plan. It pinpoints root causes from CI logs to streamline your debugging process.

What is the best way to find the root cause of a CI/CD failure in a pull request?

Finding the root cause of a CI/CD failure involves fetching and analyzing detailed GitHub Actions logs. This Skill summarizes the failure context from your pull request checks, allowing you to understand the exact error before implementing a proposed fix.

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

Yes, you must authenticate the gh CLI with repository and workflow scopes to inspect GitHub Actions logs. This authentication allows the Skill to access pull request check statuses and fetch detailed logs for failing workflows.

Does this tool work with external CI providers outside of GitHub Actions?

For external CI providers outside of GitHub Actions, this Skill only reports the details URL rather than fetching full logs. It is primarily designed to automate debugging and fixing failing checks that run natively within GitHub Actions.

What limitations should I expect when debugging failing PR checks?

A key limitation when debugging failing PR checks is that external CI providers are not fully supported; the Skill only reports their details URL. Additionally, it requires Python3 and properly configured gh CLI authentication with repo and workflow scopes.