gh-fix-ci

Inspect GitHub Actions PR checks and logs to diagnose CI failures.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill gh-fix-ci-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/github/skills/gh-fix-ci
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill gh-fix-ci-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses the friction of debugging failing GitHub Actions workflows by automating the retrieval of logs and identifying the root cause of CI failures directly from the command line.

Core Features & Use Cases

  • Automated Log Inspection: Fetches and parses logs from failing GitHub Actions runs to extract specific error snippets.
  • Contextual Analysis: Combines PR metadata with CI failure data to provide a comprehensive view of why a build failed.
  • Use Case: When a developer encounters a red checkmark on a pull request, this skill can be used to instantly pinpoint the exact line of code or test failure causing the build to break.

Quick Start

Use the gh-fix-ci skill to inspect the failing checks on the current pull request and summarize the root cause.

Frequently Asked Questions about gh-fix-ci

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

FAQPage Schema
How do I automate debugging of failing GitHub Actions CI workflows?

To automate debugging of failing GitHub Actions CI workflows, you can use a script that programmatically fetches and parses CI logs to extract error snippets and identify root causes. It automates log retrieval and pinpoints exact failures.

How do I find the root cause of a GitHub Actions build failure on a pull request?

Finding the root cause of a GitHub Actions build failure involves inspecting PR checks and parsing CI log outputs. By combining PR metadata with failure data, you can pinpoint the exact line of code or test causing the break.

Do I need GitHub CLI authentication to inspect CI logs for pull requests?

Yes, you need GitHub CLI authentication and access to repository workflow scopes to inspect CI logs. This access is required to perform programmatic log retrieval and analyze failing Actions runs within your Git repositories.

Can I use Python to extract error snippets from GitHub Actions logs?

Yes, you can use Python scripts to extract error snippets from GitHub Actions logs. Python can programmatically retrieve and parse logs from failing runs to identify the specific build errors causing your CI checks to fail.

What's the best way to resolve failing CI checks without reading full build logs?

The best way to resolve failing CI checks without reading full logs is to use automated log inspection that fetches and parses outputs to extract specific error snippets. This provides a contextual analysis of why the build failed.

Why does my GitHub Actions automation fail to retrieve CI logs?

GitHub Actions automation fails to retrieve CI logs when there is missing GitHub CLI authentication or insufficient repository workflow scopes. Proper access is required to perform log retrieval and analyze failing runs within Git repositories.