ci-failure-analyzer

Analyze GitHub Actions CI failures and generate structured failure reports.

Updated Dec 19, 2023
One-click install
npx skills add https://github.com/mintiti/pyrat-rust --skill ci-failure-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-failure-analyzer
Source: https://github.com/mintiti/pyrat-rust/tree/main/.claude/skills/ci-failure-analyzer
Command: npx skills add https://github.com/mintiti/pyrat-rust --skill ci-failure-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly diagnose GitHub Actions CI failures on the active branch, reducing the time spent sifting through logs and manual checks.

Core Features & Use Cases

  • Current-branch CI checks: List recent runs for the active branch and highlight failures.
  • Detailed failure logs: Retrieve and filter logs to show error messages and stack traces.
  • Root-cause insights: Parse logs to determine which step, test, or environment caused the failure.
  • Use Case: When a PR's CI fails after a merge, run this Skill to generate a concise failure report you can share with the team.

Quick Start

Run the following sequence in your repo to surface the latest CI failures on the current branch and view a structured report:

  • git rev-parse --abbrev-ref HEAD
  • gh run list --branch <branch-name> --limit 5
  • gh run view <run-id> --log-failed
  • gh run view <run-id> --log | grep -A 20 "FAILED|ERROR"
  • Present the findings in a summary report

Frequently Asked Questions about ci-failure-analyzer

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

FAQPage Schema
How do I diagnose GitHub Actions CI failures on my branch?

GitHub Actions CI failures can be diagnosed by listing recent workflow runs for your branch, then retrieving and parsing logs to identify which step failed and why. This Skill aggregates that data into a structured failure report showing error messages, stack traces, and environment details.

Can I analyze CI logs to find the root cause of test failures?

Yes. Parse CI logs for error messages and stack traces to pinpoint which test or build step failed and identify the root cause. This Skill extracts and filters logs to highlight failures and presents findings in a human-readable summary.

What's the fastest way to see why my GitHub Actions workflow failed?

Run git and GitHub CLI commands to list recent runs on your current branch, retrieve failed logs, and filter for error details. This Skill automates that sequence and delivers a concise failure report ready to share with your team.

Do I need GitHub CLI installed to check CI failure logs?

Yes. This Skill requires git and GitHub CLI (gh) to execute commands like gh run list and gh run view. Both tools must be available in your environment to retrieve workflow runs and logs from GitHub Actions.

How do I share CI failure details with my team after a PR merge?

Generate a structured failure report that includes error messages, stack traces, and environment details from your CI logs. This Skill produces a human-readable summary you can immediately share to help the team understand what went wrong.