analyze-github-ci

Analyze GitHub Actions CI failures and propose code fixes from pipeline or PR URLs.

Updated May 11, 2026
One-click install
npx skills add https://github.com/TomasGC/Meerkat --skill analyze-github-ci-tomasgc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-github-ci
Source: https://github.com/TomasGC/Meerkat/tree/main/skills/analyze-github-ci
Command: npx skills add https://github.com/TomasGC/Meerkat --skill analyze-github-ci-tomasgc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging failed GitHub Actions pipelines requires manually digging through lengthy logs to find root causes. This Skill automates failure analysis by fetching logs, categorizing errors, and proposing concrete code fixes. ## Core Features & Use Cases - Automated Log Analysis: Accepts pipeline or PR URLs, fetches failed job logs via the gh CLI, and categorizes errors into infrastructure, compilation, build, test, and lint types. - Specific Fix Proposals: Generates actionable fixes with file:line references and before/after diffs, confirmed with you before any code change is applied. - Token-Efficient Delegation: Offloads mechanical fixes (imports, syntax, assertions) to a local Ollama model, escalating complex issues to Claude. - Use Case: You paste a failed PR URL like https://github.com/owner/repo/pull/67, and the Skill identifies that lint errors and emulator timeouts caused the failure, then proposes the exact code changes to fix the lint violations. ## Quick Start Provide a GitHub Actions pipeline or pull request URL and ask to analyze the CI failures and propose fixes.

Frequently Asked Questions about analyze-github-ci

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

FAQPage Schema
How do I analyze GitHub Actions CI failures automatically?

Provide a pipeline URL (github.com/owner/repo/actions/runs/id) or PR URL, and the Skill fetches failed job logs using the gh CLI, categorizes errors, and proposes specific fixes with file and line references.

How to debug a failed GitHub pull request pipeline?

Paste the PR URL and the Skill fetches all associated workflow runs via gh pr checks, identifies failed runs, aggregates errors across them, and reports deduplicated issues with prioritized fix recommendations.

What types of CI errors can be categorized from build logs?

Errors are classified into five categories: infrastructure (emulator crashes, timeouts), compilation (syntax errors, unresolved references), build (dependency or Gradle failures), tests (assertion failures), and lint (code quality violations).

Does CI failure analysis require the GitHub CLI?

Yes, the gh CLI must be installed and authenticated to fetch run logs and PR information. If it is missing, the Skill reports installation instructions for macOS, Windows, and Linux.

Can infrastructure failures be fixed with code changes?

No. Transient infrastructure issues like emulator crashes or timeouts are flagged for workflow retry rather than code fixes. The Skill only proposes code changes for compilation, build, test, and lint errors.

Why does the analysis script fail to run?

Common causes include missing gh CLI, expired authentication, GitHub API rate limits, or the script not being found at its expected path. The Skill reports the specific error and suggests verification commands.