Triage CI failures, fix regressions
Run ci-triage on failing CI, fix clear regressions in isolation, verify before push, and update state—up to 3 attempts per cluster.
Prompt
/loop 15m Run ci-triage on failing CI for default branch and open PRs. Update ci-sweeper-state.md. Fix only clear regressions in an isolated worktree. Spawn loop-verifier before any push. Max 3 attempts per failure cluster
claude-code
Source: Harqer ↗graded B · 80/100 — how grades work (Safety Score v2) →
Similar loops
All ci loops →B
/goalCIlow risk
Get the build green
Run the build, fix the first error, and repeat until npm run build exits 0, with a 10-turn cap.
/goal `npm run build` exits 0 — run the build, fix the first error, repeat until it succeeds; stop after 10 turns
C
/goalCIlow risknew
Fix lint violations, ship clean code
Run linters on modified files and exit when zero violations remain across all changes.
/goal Phase 2 (Step C - Linter Verification): Execute targeted file-level linters to verify 0 remaining violations across all modified files (exit 0)
B
/loopCImedium risknew
Triage CI failures, fix clear regressions
Run every 15 minutes to classify CI failures, fix clear regressions in a worktree with verification, and escalate infrastructure or security test failures.
/loop 15m $ci-triage — update ci-sweeper-state.md. Classify failures first. Fix only clear regressions in a worktree with verifier. Max 3 attempts. Escalate infra and security test failures