← Gallery

Triage failing CI

Looks at the latest failing CI run for this branch, finds the first real error, and explains the likely cause and the fix.

Kind
Recipe
By
Plexiform (@CallumJB125) self-declared
License
CC0-1.0
Added
2026-10-10
Updated
2026-10-10
Stacks
any
Tools
claude
Tags
ci, debugging
sha256
c0b06775f674265b513cdf7b74bf658b551cd5b098a9d85fe5e5e542c75ff0e5

Looks at the latest failing CI run for this branch, finds the first real error, and explains the likely cause and the fix.

Read-only: it plans and reports, and never changes files. Cost: Low to medium: reads CI logs, which can be long.

The prompt

Triage the failing CI for the current branch.

1. If the GitHub CLI is available, run `gh run list --branch "$(git branch --show-current)" --limit 5` and `gh run view <id> --log-failed` for the latest failed run. Otherwise read the CI config (.github/workflows, .gitlab-ci.yml and so on) and run the same steps locally.
2. Find the first real error, not the noise after it.
3. Decide whether it is a code bug, a flaky test, an environment or secret problem, or a dependency change, and show the evidence.
4. Say exactly what to change to fix it, with file and line.

Do not change any files, re-run jobs or push.

To add it: in Plexiform, open Discover in the sidebar, then Add. You see everything it contains before anything is saved.