gh-fix-ci

Diagnose and fix failing GitHub Actions checks on pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When a user asks to debug or fix failing GitHub Actions checks on a pull request, this skill coordinates PR metadata retrieval via a GitHub app with the gh CLI to inspect checks and logs, then surfaces a concise root cause and an actionable fix plan.

Core Features & Use Cases

  • Hybrid PR context: leverages GitHub app-provided PR metadata and gh-based log inspection to identify failing checks with context.
  • Root-cause-first workflow: summarizes the failure, proposes a focused fix plan, and implements only after explicit approval.
  • Safe, iterative remediation: guides authentication, verification, and recheck steps to minimize regressions and ensure traceability.

Quick Start

Investigate a failing PR by inspecting PR metadata and Actions logs with gh, then propose and apply an approved fix.

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?

Debug failing GitHub Actions checks by combining GitHub app PR metadata with gh CLI log inspection to surface root causes. This approach summarizes failures, proposes a focused fix plan, and verifies status after applying approved changes locally.

How do I analyze GitHub Actions logs to find the root cause of a CI failure?

Analyze GitHub Actions logs by pulling PR metadata and check runs via gh CLI. This surfaces the failing check context, allowing you to isolate the exact CI failure root cause before implementing any code changes.

Do I need to authenticate the gh CLI to inspect pull request check runs?

Yes, you need to authenticate the gh CLI to inspect pull request check runs. Authentication grants the required access to pull PR metadata, retrieve Actions logs, and verify the recheck status after applying fixes.

Can I use this approach to fix CI failures on GitHub-hosted runners?

Yes, you can fix CI failures on GitHub-hosted runners. This diagnostic workflow applies to PR-level CI failures across GitHub-hosted runners by inspecting logs and guiding safe, iterative remediation to minimize regressions.

How does this workflow handle external checks that fail on my pull request?

When external checks fail on your pull request, the workflow handles them gracefully by focusing on GitHub Actions logs and PR metadata. It ensures a focused repair plan without failing on unsupported external check configurations.

What is the safest way to apply fixes for failing PR checks locally?

The safest way to apply fixes for failing PR checks is an iterative remediation workflow that proposes a focused fix plan, implements changes only after explicit approval, and runs verification rechecks to ensure traceability and minimize regressions.