diagnose-cilisted

# Diagnose and fix GitHub Actions CI failures Project-agnostic, global skill. It fetches the latest GitHub Actions failure logs, reproduces the failure locally, classifies the root cause, proposes a concrete fix, and — after approval — applies it and offers to re-trigger CI via commit + push. It is the operational companion to `$setup-ci`: that skill builds the pipeline; this one keeps it green. ## Failure taxonomy (classify before diagnosing) Identifying the failure class first prevents wasted effort — the remediation is completely different for each class: | Class | Signals | Remedy | |---|---|---| | **Code bug** | assertion error, compile error, lint error in a source file | fix the code | | **Flaky test** | same job failed intermittently across unrelated commits | quarantine test or add retry | | **Infra / config** | "rate limit", "connection refused", "secret not found", "runner", "out of disk", "timeout" in system-level output | fix workflow config, rotate secret, re-run | | **Matrix-specific** | fails on one version/OS cell, passes on others | version-specific code or env issue | | **Stale dependency** | lock-file mismatch, registry error, version range now broken | update dependency or pin version | Always classify first; never jump to fixing code when the failure is infra. ## Procedure ### 1. Auth guard - Run `gh auth status`. If not authenticated, tell the user to run `gh auth login` (or `! gh auth login` to run it in this session), then stop — do not proc