gh-fix-ci

Debug failing GitHub PR checks and draft approval-gated fix plans.

779|80|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Haohao-end/openagent --skill gh-fix-ci-haohao-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/gh-fix-ci
Command: npx skills add https://github.com/Haohao-end/openagent --skill gh-fix-ci-haohao-end

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill helps debug and plan fixes for failing GitHub PR checks so teams can quickly identify the root failure and move toward a verified solution without blindly changing CI.

Core Features & Use Cases

  • Locate failing checks: Finds which GitHub Actions checks on a pull request have failed, errored, or are still requiring action.
  • Extract actionable evidence: Pulls workflow/run metadata and retrieves log output, including fallbacks when some log fields drift or logs are temporarily unavailable.
  • Plan first, implement after approval: Produces a concise failure summary, then drafts a fix plan and asks for explicit approval before implementation.
  • Out-of-scope provider handling: Detects non-GitHub Actions “details” links and reports only the details URL instead of attempting to operate on other CI providers.

Quick Start

Ask the AI to run the skill to inspect your PR, summarize the failing check logs, and draft an approval-required fix plan.

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, this Skill locates failed workflows, fetches run metadata, and extracts focused failure log snippets to provide clear root-cause context for your pull request.

What is the best way to extract error logs from failed PR checks without blindly changing CI?

The best way to extract error logs safely is by retrieving workflow metadata and job-log fallbacks, summarizing the failure, and drafting an approval-gated fix plan before making any CI changes.

Do I need GitHub CLI authentication to analyze pull request checks?

Yes, you need GitHub CLI authentication. The Skill uses gh commands to resolve the target pull request, enumerate checks, and retrieve logs for CI troubleshooting.

Can I use this to fix CI failures from external providers linked in the PR details?

No, for non-GitHub Actions providers, the Skill detects external details links and reports only the URL, as it specifically targets GitHub Actions workflows and logs.

How does the approval-gated remediation workflow handle CI fixes?

The approval-gated workflow produces a concise failure summary and drafts a fix plan, then requires your explicit approval before implementing any changes to ensure safe remediation.

Why does my GitHub Actions log retrieval fail when some log fields drift?

Log retrieval may fail when log fields drift or are temporarily unavailable, so the Skill applies job-log fallbacks to extract actionable evidence and ensure you still get the failure context.