debug-failing-cilisted
Install: claude install-skill tmj-90/gaffer
# Debug a failing CI pipeline
A red pipeline measures a difference: between your machine and the runner, between two
commits, or between two runs of the same commit. Find the difference, fix what it
reveals, and never make CI green by making it look away.
**How this works in Gaffer.** You never push and cannot re-run CI yourself. The runner
pushes your branch and opens a PR only when the operator has enabled that, and only
then can its opt-in CI gate run: a red check sends the delivery back to rework with the
failing check attached as evidence. So your proof is a local reproduction under CI's
exact conditions — fails before, passes after — and any later CI run is the runner's.
## Steps
1. **Get the real failure text.** Read `get_ticket` (the description,
`last_review_feedback` and `latest_events`) plus any review-feedback block in your
prompt. Find the FIRST error in the log, not the
last — later failures are usually consequences. Note the step, the exact command, and
the exit code. Call `search_lore` for known CI gotchas in this repo. If only a check
name and URL are available and you cannot open the log (no network or credentials),
go on to step 3 anyway: the workflow file tells you what CI ran.
2. **Classify before fixing.** Each class has a different fix:
- **code / test** — the change is wrong, or a test encodes stale behaviour;
- **flake** — passes and fails on the same commit (order, time, shared state, network);
- **environment drift** —