It retrieves and parses failed CI logs to summarize specific errors and failing test cases.
Install
mkdir -p .claude/skills/analyze-ci && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2952" && unzip -o skill.zip -d .claude/skills/analyze-ci && rm skill.zipInstalls to .claude/skills/analyze-ci
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyze failed GitHub Action jobs for a pull request.Key capabilities
- →Fetch logs from failed GitHub Action jobs
- →Identify root causes and specific error messages
- →Extract pytest test names from logs
- →Generate per-job failure summaries
- →Provide paths to raw and failed-step logs
How it works
The skill fetches logs using a package-specific command and then parses the failed-step log to identify root causes and error details.
Inputs & outputs
When to use analyze-ci
- →Debug failing pull request CI jobs
- →Summarize root causes of test failures
- →Identify package version issues in builds
About this skill
Analyze CI Failures
Fetch logs from failed GitHub Action jobs and produce a focused per-job failure summary.
If no URLs are passed as arguments, use the relevant job, run, or PR URLs already shared in the conversation. If none are available, ask for a URL and stop.
Steps
-
Fetch logs with the following command. Single-quote each URL to protect shell special characters like
?.uv run --package skills skills fetch-logs '<url1>' ['<url2>' ...] -
Read all reported ranges. Inspect the raw log directly if no failed-step range is available, then identify:
- The root cause and its impact.
- A short log excerpt showing the failure.
- A full node ID for pytest failures (e.g.
tests/test_foo.py::test_bar[case1]). - Package versions or snapshot changes that help explain the failure.
-
Format each job with a heading, an evidence list, and a summary of 1-2 sentences plus the log excerpt.
## <workflow name> / <job name> - URL: <job_url> - Raw log: <raw_log_path> - <additional fields, if present> <summary>Copy the raw log path verbatim from step 1. If no failed step is recorded, include the reported
Conclusion:field too.
When not to use it
- →When the job URL is not for a GitHub Action
Prerequisites
Limitations
- →Requires specific URL formats for GitHub Action jobs
- →Relies on the availability of cached log files
How it compares
Unlike manual log inspection, this skill automatically aggregates failure data and formats it into a structured summary for debugging.
Compared to similar skills
analyze-ci side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| analyze-ci (this skill) | 1 | 6mo | Review | Intermediate |
| moai-workflow-testing | 1 | 5mo | Review | Intermediate |
| sentry-pr-code-review | 0 | 6mo | Review | Intermediate |
| python-testing-patterns | 77 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mlflow
View all by mlflow →You might also like
moai-workflow-testing
modu-ai
Comprehensive development workflow specialist combining DDD testing, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
sentry-pr-code-review
richardadonnell
Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
codex-claude-loop
bear2u
Orchestrates a dual-AI engineering loop where Claude Code plans and implements, while Codex validates and reviews, with continuous feedback for optimal code quality
shellcheck-configuration
wshobson
Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.