github-fix-ci

Diagnoses GitHub Actions check failures and generates remediation plans with verification steps.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill github-fix-ci-kentoshimizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-fix-ci
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/github-fix-ci
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill github-fix-ci-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Move failed CI checks from symptoms to verified root-cause fixes without bypassing quality gates.

Core Features & Use Cases

  • Automated triage of failing PR checks with evidence links and failure context.
  • Classification using a standard CI failure taxonomy and reusable triage templates.
  • Workflow-driven remediation planning and verification via targeted scripts.

Quick Start

Run the triage workflow on a failing PR by executing the inspection script and recording results with the provided templates.

Frequently Asked Questions about github-fix-ci

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

FAQPage Schema
How do I diagnose failing GitHub Actions checks on a pull request?

Diagnosing failing GitHub Actions checks involves running a guided triage workflow that inspects PR check data, classifies the root cause using a standard CI failure taxonomy, and generates a remediation plan. It requires gh authentication to access pull request check data.

What is evidence-based triage for CI failures?

Evidence-based triage for CI failures is a guided workflow that records findings with evidence links and failure context to isolate root causes. It moves failed checks from symptoms to verified root-cause fixes without bypassing quality gates.

Do I need gh authentication to triage failing PR checks?

Yes, you need gh authentication to triage failing PR checks. Access to PR check data is required to run the inspection script, record results with reusable templates, and generate verification steps.

How do I classify root causes for GitHub Actions failures?

You can classify root causes for GitHub Actions failures using a defined CI failure taxonomy. The triage workflow applies this standard classification to recorded findings and produces a targeted remediation plan.

What's the best way to plan remediation for failing CI checks?

The best way to plan remediation for failing CI checks is using a workflow-driven approach that generates a remediation plan with verification steps. This ensures fixes are verified against evidence links and failure context.