gh-fix-ci

Diagnose failing GitHub Actions PR checks and propose remediation plans.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/misty-step/harness-kit --skill gh-fix-ci-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/misty-step/harness-kit/tree/main/skills/.external/openai-gh-fix-ci
Command: npx skills add https://github.com/misty-step/harness-kit --skill gh-fix-ci-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps engineers quickly diagnose and fix failing GitHub PR checks by extracting actionable failure details, summarizing the context, and guiding remediation.

Core Features & Use Cases

  • Inspect failing PR checks via gh, fetch and summarize failure context, and draft a remediation plan for reviewer approval.
  • Generate an approval-ready fix plan and, after explicit consent, apply changes and re-check status.
  • Focus on GitHub Actions-based checks; external providers are out of scope and only the details URL is reported when applicable.

Quick Start

Automatically inspect failing PR checks using gh, summarize failure context, and draft a plan for fixes.

Frequently Asked Questions about gh-fix-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose failing GitHub Actions checks on a pull request?

This Skill inspects failing GitHub Actions checks by fetching and summarizing log context via gh, then drafting a remediation plan for your review before any changes are applied.

Can I automatically fix GitHub PR checks without manual review?

You cannot automatically apply changes without explicit consent; this Skill generates an approval-ready fix plan and only modifies your code to re-check status after you provide explicit user approval.

Do I need gh authentication to analyze GitHub Actions log failures?

Yes, you need gh authentication and access to repo PR data to parse detailsUrl, locate runs, and extract failure context from GitHub Actions logs for diagnosis.

Does this tool diagnose CI failures from external providers like Jenkins?

No, it focuses exclusively on GitHub Actions-based checks; external CI providers are out of scope and only the details URL is reported when applicable for those checks.

What is the best way to extract actionable failure details from GitHub Actions logs?

The best way to extract failure details is using gh to pull actionable context from GitHub Actions logs, summarize the failing checks, and propose a concise remediation plan for approval.