skills.rest
KaiserWhoLearns
KaiserWhoLearnsCOMMUNITY
Explore all skills by this author →
Website𝕏@KaiserWhoLearnsGitHub

analyze-ci

Analyze failed GitHub Action jobs and summarize root causes from PR URLs.

Updated Jan 15, 2026
Search Tags:#automation#logs#github#debug#analyze#ci#pull-request
One-click install
npx skills add https://github.com/KaiserWhoLearns/skillsbench --skill analyze-ci-kaiserwholearns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-ci
Source: https://github.com/KaiserWhoLearns/skillsbench/tree/main/tasks/fix-build-agentops/environment/skills/analyze-ci
Command: npx skills add https://github.com/KaiserWhoLearns/skillsbench --skill analyze-ci-kaiserwholearns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze failed GitHub Action jobs and identify root causes for a PR to speed up triage and fixes.

Core Features & Use Cases

  • Unified failure summaries: Collects logs, errors, and job names from failed CI runs and presents a concise root-cause report.
  • PR-focused analysis: Works across multiple workflow runs in a pull request to surface common failure patterns.
  • Debug-ready outputs: Optionally includes tokens and costs or debug traces when requested.

Quick Start

Launch uv run skills analyze-ci <pr_url> to generate a concise failure summary for the PR.

Frequently Asked Questions about analyze-ci

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

FAQPage Schema
How do I analyze CI failures from a GitHub pull request?▼

To analyze CI failures from a GitHub pull request, provide a PR URL to generate a concise failure summary. This tool parses logs from multiple failed GitHub Action jobs to identify root causes and accelerate fixes.

How do I debug multiple failed GitHub Action jobs in a PR workflow?▼

To debug multiple failed GitHub Action jobs in a PR workflow, use a PR URL to surface common failure patterns. It collects logs and errors across workflow runs to produce a concise root-cause report for quick triage.

Can I get debug traces and tokens from failed GitHub Action logs?▼

Yes, you can get debug traces and tokens from failed GitHub Action logs. The analysis optionally includes debug information and costs when requested to help you quickly triage and fix CI failures.

What is the best way to triage CI failures across multiple workflows in one PR?▼

The best way to triage CI failures across multiple workflows in one PR is to use a unified failure summary. It analyzes the PR URL to collect logs from failed runs and presents a concise root-cause report.

Does this CI failure analysis work with individual GitHub Action job URLs?▼

Yes, this CI failure analysis works with individual GitHub Action job URLs. It can parse logs from individual job URLs as well as entire PR URLs to identify and summarize root causes of failed runs.

Related Skills

Explore More Software Engineering Skills→
syl2042syl2042

gh-fix-ci

Diagnose failing GitHub Actions PR checks and draft actionable fix plans.

Community
Advanced
gsarmaonlinegsarmaonline

review-comments

Analyze pull request review comments and resolve failing GitHub Actions checks.

Community
Advanced
akin-ozerakin-ozer
290

github-actions-validator

Validate GitHub Actions workflows with actionlint and act before deployment.

Community
Advanced
paultyngpaultyng
9

ci-debug-loop

Diagnose failing GitHub Actions runs, apply fixes, and re-trigger CI.

Community
Advanced