gh-fix-ci

Inspect failing GitHub Actions checks and propose fix plans.

Updated Dec 25, 2019
One-click install
npx skills add https://github.com/boga/dotfiles --skill gh-fix-ci-boga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fix-ci
Source: https://github.com/boga/dotfiles/tree/main/templates/opencode/skills/gh-fix-ci
Command: npx skills add https://github.com/boga/dotfiles --skill gh-fix-ci-boga

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, saving developers time and effort in identifying and fixing issues.

Core Features & Use Cases

  • Automated Check Inspection: Uses gh CLI to identify failing checks on GitHub PRs.
  • Log Retrieval: Fetches logs for failing GitHub Actions to pinpoint the root cause.
  • Failure Summarization: Provides concise summaries of failure snippets from logs.
  • Fix Planning: Integrates with a plan skill to create and implement a fix.
  • Use Case: When a PR fails its CI checks, this Skill can automatically investigate, provide a summary of the error, and propose a plan to fix it, which the developer can then approve and apply.

Quick Start

Use the gh-fix-ci skill to inspect the failing checks for the current branch's 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 on a pull request, you need to inspect check statuses and pull relevant logs. This Skill automates that by using the gh CLI to fetch logs, summarize failure contexts, and propose a fix plan.

Can I automatically retrieve GitHub Actions logs to find the root cause of a PR failure?

Yes, you can automatically retrieve GitHub Actions logs to find the root cause of a PR failure. This Skill fetches logs for failing GitHub Actions checks, pinpoints the root cause, and provides concise summaries of failure snippets.

Do I need the gh CLI authenticated to inspect failing CI checks?

Yes, you need the gh CLI authenticated with appropriate scopes to inspect failing CI checks. This Skill specifically relies on the authenticated gh CLI to identify failing checks and pull relevant GitHub Actions logs.

What is the best way to summarize GitHub Actions failure contexts for a fix plan?

The best way to summarize GitHub Actions failure contexts for a fix plan is to automate log retrieval and failure summarization. This Skill extracts concise failure snippets from GitHub Actions logs and proposes a targeted fix plan.

Does this CI/CD debugging approach work with external providers like Buildkite?

No, this CI/CD debugging approach does not work with external providers like Buildkite. It specifically targets GitHub Actions and scopes out external CI providers to focus on automating GitHub PR check debugging.