gh-fix-ci

Extract failure details from GitHub Actions CI logs for pull requests.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/wyhlovecpp/my-codex-settings --skill gh-fix-ci-wyhlovecpp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/wyhlovecpp/my-codex-settings/tree/main/skills/by-category/git-github/pr-automation/gh-fix-ci
Command: npx skills add https://github.com/wyhlovecpp/my-codex-settings --skill gh-fix-ci-wyhlovecpp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers and DevOps teams quickly identify, analyze, and troubleshoot failed GitHub Actions CI checks, reducing downtime and manual log searches.

Core Features & Use Cases

  • Log Retrieval and Analysis: Fetches detailed logs from recent CI runs related to pull requests and highlights failure points.
  • Failure Snippet Extraction: Extracts relevant sections of logs around failure markers to facilitate rapid debugging.
  • Use Case: When a pull request’s CI checks fail unexpectedly, use this Skill to automatically retrieve logs, pinpoint errors, and generate concise reports for faster resolution.

Quick Start

Use the gh-fix-ci skill to analyze recent failed GitHub Actions runs associated with your pull request and get quick insights into the root causes.

Frequently Asked Questions about gh-fix-ci

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

FAQPage Schema
How do I automatically extract failure details from GitHub Actions CI logs?

To extract failure details from GitHub Actions CI logs, fetch the pull request run logs and parse them for error markers. This Skill automates log retrieval and highlights relevant failure snippets to accelerate debugging workflows.

What is the best way to troubleshoot unexpected CI failures for a pull request?

Troubleshooting CI failures for a pull request involves retrieving the specific run logs and isolating the error context. This skill automatically parses CI logs to pinpoint exact failure points and generate concise reports for rapid resolution.

Do I need PyYAML and requests to automate GitHub Actions debugging?

Yes, you need PyYAML and requests installed in your environment to automate GitHub Actions debugging. These dependencies enable the API interactions and configuration parsing required for extracting CI failure logs.

Can I generate concise failure reports for failed GitHub Actions CI runs?

Yes, you can generate concise failure reports for failed GitHub Actions CI runs. By extracting relevant log sections around failure markers, the skill provides detailed reporting to help developers quickly identify root causes.

What are the limitations of using automated CI log parsing for GitHub Actions?

Automated CI log parsing for GitHub Actions is limited to extracting failure snippets from accessible run logs. It focuses on identifying error markers and does not inherently fix code-level issues or execute remediation steps automatically.