gh-fix-ci

Inspect failing GitHub PR checks and generate a fix plan.

1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Sologa/codex-pipeline --skill gh-fix-ci-sologa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/Sologa/codex-pipeline/tree/main/.codex/skills/gh-fix-ci
Command: npx skills add https://github.com/Sologa/codex-pipeline --skill gh-fix-ci-sologa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the debugging of failing CI/CD checks on GitHub Pull Requests, reducing the time spent on diagnosing and fixing build and test failures.

Core Features & Use Cases

  • Automated Failure Analysis: Inspects GitHub PR checks, fetches logs for failing GitHub Actions, and summarizes the failure context.
  • Plan Generation: Creates a step-by-step plan to address the identified issues.
  • Use Case: When a pull request fails its CI checks, this Skill can automatically pull the relevant logs, pinpoint the error, and propose a fix, allowing developers to quickly resolve the issue and merge their code.

Quick Start

Use the gh-fix-ci skill to inspect the failing CI 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, use this Skill to automate fetching PR logs via the `gh` CLI, summarize failure context, and generate a fix plan. It scopes external checks and pinpoints actionable errors for quick resolution.

Can I automatically generate a fix plan for failing CI/CD pipelines?

Yes, you can automatically generate a fix plan for failing CI/CD pipelines. The Skill inspects failing GitHub PR checks, fetches logs, summarizes failure context, and proposes a step-by-step plan for user approval.

Do I need `gh` CLI authentication to troubleshoot GitHub Actions logs?

Yes, you need `gh` CLI authentication to troubleshoot GitHub Actions logs. The Skill requires escalated permissions through the `gh` CLI to fetch logs and inspect failing PR checks effectively.

What is the best way to automate GitHub Actions troubleshooting for external checks?

The best way to automate GitHub Actions troubleshooting is using this Skill to scope external checks and fetch logs. It identifies actionable failures within GitHub Actions and summarizes the context for quick fixes.

Why does this CI/CD debugging process require user approval before applying fixes?

The CI/CD debugging process requires user approval because it generates a step-by-step fix plan after analyzing failures. This ensures developers maintain control over code changes before resolving GitHub PR check errors.