Analyze failed GitHub Action jobs in pull requests to identify root causes.
npx skills add https://github.com/mlflow/dev --skill analyze-ci
Please help me install this Agent Skill. Skill: analyze-ci Source: https://github.com/mlflow/dev/tree/main/.claude/skills/analyze-ci Command: npx skills add https://github.com/mlflow/dev --skill analyze-ci
This skill analyzes failed GitHub Action jobs in a pull request to quickly identify root causes and relevant logs.
uv run skills analyze-ci <pr_url> uv run skills analyze-ci <job_url> [job_url ...] uv run skills analyze-ci <pr_url> --debug
High-intent search queries and answers about installing and using this skill.
Analyzing failed GitHub Actions jobs identifies root causes by evaluating all failed jobs in a pull request or specific job URLs, outputting a concise failure summary from the relevant logs.
You can debug a specific failed GitHub Actions job by passing the job URL directly to the analyzer, which isolates the failure and outputs relevant logs without evaluating the entire PR workflow.
Yes, a GitHub token is required to analyze CI failures and is auto-detected via the gh auth token command or set explicitly using the GH_TOKEN environment variable for secure repository access.
Yes, you can view detailed debug output when analyzing failed GitHub Actions jobs by passing the --debug flag alongside the pull request URL to generate more verbose diagnostic logs.
The best way to surface common issues across multiple failed GitHub Actions jobs is to perform a PR-wide failure analysis that assesses all failed jobs simultaneously to identify shared root causes.
devMoezConfigure GitHub authentication for git operations and API access.
jMertaDiagnose and patch failing GitHub Actions CI workflows using the GitHub CLI.
josuenavarroaguadoAutomate GitHub Actions CI/CD pipelines with quality gates and preview deployments.
HomericIntelligenceParse and categorize CI failure logs to identify root causes.
