agentleFS
ControllableModelControllableModel/SWE-Skills-Bench/skills/analyze-ci/SKILL.md

analyze-ci

Skill8 starsChanged 27 days agoMITView on GitHub

Analyze failed GitHub Action jobs for a pull request.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Analyze CI Failures

This skill analyzes logs from failed GitHub Action jobs using Claude.

Prerequisites

  • GitHub Token: Auto-detected via gh auth token, or set GH_TOKEN env 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.