skills.rest
GeneralReasoning
GeneralReasoningOFFICIAL
Explore all skills by this author →
Website𝕏@GenReasoningGitHub

analyze-ci

Analyze failed GitHub Actions jobs for a pull request and output a failure summary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify the root causes of failed CI jobs on a pull request by parsing logs and error messages, saving time debugging and accelerating PR reviews.

Core Features & Use Cases

  • Analyze all failed jobs in a PR to produce a concise summary with root cause, key errors, and affected tests.
  • Analyze specific job URLs to drill down on individual failures.
  • Output structured results suitable for quick triage and handoff to engineers.

Quick Start

Run uv run skills analyze-ci <pr_url> to generate a concise failure report for the pull request.

Frequently Asked Questions about analyze-ci

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

FAQPage Schema
How do I find the root cause of a GitHub Actions failure on a pull request?▼

To find the root cause of a GitHub Actions failure, you can analyze failed jobs on a pull request to parse logs and identify key errors, producing a concise failure summary with root causes and relevant log snippets.

Can I analyze specific failed GitHub Actions jobs instead of all jobs in a PR?▼

Yes, you can analyze specific failed GitHub Actions jobs by providing individual job URLs to drill down on individual failures, or analyze all failed jobs in the pull request at once.

Do I need a GitHub token to analyze CI failures?▼

Yes, you need a GitHub token to analyze CI failures. The token is auto-detected from your environment or can be set using the GITHUB_TOKEN environment variable.

What information is included in the CI failure analysis output?▼

The CI failure analysis output includes a concise failure summary featuring the root cause, error messages, affected test names, and relevant log snippets for quick triage.

How do I run a diagnosis for failed CI jobs from the command line?▼

To run a diagnosis for failed CI jobs, execute the command uv run skills analyze-ci with your pull request URL to generate a concise failure report.

Related Skills

Explore More Software Engineering Skills→
granietgraniet
247

github-auth

Automates GitHub authentication setup for git, SSH, gh CLI, and API access.

Community
Intermediate
joshka0joshka0
3

foxctl CI

Retrieve GitHub pull request CI check outcomes and review comments.

Community
Basic
mvillmowmvillmow
18

analyze-ci-failure-logs

Analyze CI failure logs to identify root causes and error patterns.

Community
Intermediate
yalehyaleh
21

build-quality-gates

Automates BUILD file linting and CI/CD checks for changed projects.

Community
Advanced