check-ci

Diagnose and fix failing GitHub Actions CI runs for the current branch.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/easyspace-ai/minote --skill check-ci-easyspace-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-ci
Source: https://github.com/easyspace-ai/minote/tree/main/.claude/skills/check-ci
Command: npx skills add https://github.com/easyspace-ai/minote --skill check-ci-easyspace-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes failing GitHub Actions CI runs for the current branch.

Core Features & Use Cases

  • Inspect the latest GitHub Actions run, report job statuses, and collect failed logs.
  • Automatically diagnose failures and commit fixes back to the branch.
  • Provide guidance to speed up remediation and ensure CI health.

Quick Start

Run the skill on a repository to automatically diagnose and fix failing GitHub Actions CI runs for the current branch.

Frequently Asked Questions about check-ci

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

FAQPage Schema
How do I automatically diagnose and fix failing GitHub Actions CI runs?

Automating GitHub Actions CI diagnosis involves fetching the latest run for your current branch, extracting failed job logs, interpreting the JSON data, and pushing patch commits directly back to the repository.

Can I automatically extract logs and commit fixes for multiple GitHub Actions runners?

Yes, extracting logs and committing fixes works for workflows across multiple runners. The process inspects job statuses, collects failed logs, diagnoses the root cause, and applies automated patches to ensure CI health.

Do I need the gh CLI and git installed to automate CI failure fixes?

Yes, both the gh and git command-line tools must be available in your environment. These dependencies are required to fetch GitHub Actions run data, interpret JSON outputs, and push automated fixes back to the branch.

What is the best way to speed up remediation for a failing GitHub Actions workflow?

The best way to speed up GitHub Actions remediation is to automate log extraction and failure diagnosis. By automatically identifying the root cause and committing a targeted fix, you minimize manual debugging and restore CI health faster.

Why does my automated CI fix process require access to the GitHub repository?

Automated CI diagnosis requires repository access to fetch the latest GitHub Actions runs, read workflow JSON data, extract failed logs, and ultimately push the diagnostic fixes back to the current branch.