# CI Triage

> How to respond when a CI check goes red, a PR check fails, a test is flaky, or a job times out. Activate whenever a check is red or cancelled, a workflow run failed, a test is intermittent, you are about to claim a PR is green or mergeable, or you are about to re-run a job. The load-bearing rule is that a red check is a bug you have not diagnosed yet — "flake", "pre-existing", "unrelated", and "infra" are conclusions you must earn by reading the log, never opening assumptions, and never a licence to re-run. Also covers the one genuine exception (a red on a SHA a newer push superseded) and how to tell it apart from a real failure. Distinct from .github/CLAUDE.md, which owns how to AUTHOR a workflow rather than how to react to one.

## Facts
- Page: https://tashan.sh/capability/skill-alexandermattturner-ci-triage
- tashan id: skill:AlexanderMattTurner/ci-triage
- Source: https://github.com/AlexanderMattTurner/agent-sanitizer
- Type: skill
- Category: devtools
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 100.0
- Freshness: 99.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: Apache-2.0
- Official: no

## Install

```sh
cp -r ci-triage ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-14 by tashan (https://tashan.sh) from public evidence. Scorer s5.