analyze-ci
Analyze failed GitHub Action jobs for a pull request.
When & Why to Use This Skill
This Claude skill automates the analysis of failed GitHub Action jobs within pull requests. By leveraging AI to parse extensive CI logs, it identifies root causes, extracts specific error messages, and provides concise summaries, significantly reducing the time developers spend troubleshooting pipeline failures.
Use Cases
- Automated Pull Request Debugging: Quickly pinpoint the exact cause of CI failures in a PR without manually scrolling through thousands of lines of logs.
- Error Extraction and Summarization: Automatically isolate relevant log snippets, failed test names, and specific error codes to provide actionable insights for developers.
- CI/CD Pipeline Optimization: Identify recurring infrastructure issues or flaky tests by analyzing job logs across different runs to improve overall build stability.
| name | analyze-ci |
|---|---|
| description | Analyze failed GitHub Action jobs for a pull request. |
| - Bash(uv run skills analyze-ci | *) |
Analyze CI Failures
This skill analyzes logs from failed GitHub Action jobs using Claude.
Prerequisites
- GitHub Token: Auto-detected via
gh auth token, or setGH_TOKENenv var
Usage
# Analyze all failed jobs in a PR
uv run skills analyze-ci <pr_url>
# Analyze specific job URLs directly
uv run skills analyze-ci <job_url> [job_url ...]
# Show debug info (tokens and costs)
uv run skills analyze-ci <pr_url> --debug
Output: A concise failure summary with root cause, error messages, test names, and relevant log snippets.
Examples
# Analyze CI failures for a PR
uv run skills analyze-ci https://github.com/mlflow/mlflow/pull/19601
# Analyze specific job URLs directly
uv run skills analyze-ci https://github.com/mlflow/mlflow/actions/runs/12345/job/67890