cilooplisted

# Ciloop Drive a failing CI run to **green**. Pull the real error from the logs, reproduce it **locally**, fix the failures you're confident about, push **once**, and confirm — looping until green. **Core principle:** CI is slow and costs minutes, so don't use it as your edit-test loop. **Reproduce the failure locally, fix until local is green, then push once.** And don't flail: fix what you can diagnose with confidence; for failures you can't (flaky, infra, secrets, ambiguous logic), **stop and hand back** rather than guess. Loop the fixable; hand back the judgment calls. ## When to use - A push/PR has red checks and you want them green without babysitting each run. - "Fix the failing CI", "make the checks pass", "CI is red, loop until it's clean". **When NOT to use:** You only want to *read* why CI failed without fixing → just `gh run view --log-failed`. The failures are all infra/deploy/flaky (nothing to fix in code) → ciloop will just hand those back. ## Classify every failure first | Category | Examples | Action | |---|---|---| | **Confident-fix** | lint, format/prettier, type errors (tsc), clear test/assertion failures, missing import, obvious compile error | reproduce locally → fix → loop | | **Hand-back** | flaky/non-deterministic tests, infra/network timeouts, missing secrets/credentials, deploy/release steps, ambiguous logic failures you can't pin down | **don't touch** — record the real error + why, report at the end | A step that **can't run locally** (nee