Keep Loops RunningLoops is going viral and we need your help to keep the project free and alive.

loops!
BrowseSign in
Back to loops
CI
interval
CursorClaude Code

CI Failure Watcher

Poll CI on an interval, investigate failures when checks go red, and push fixes until green.

2k views1.2k installs

by loops!

Use loop copies the kickoff. Share copies the loop link. Open in Cursor / Claude Code only pre-fill that prompt — they do not install hook files. Click Install files, extract the zip into your repo, then restart your agent. How it works

Guardrails
Hardened
Anti-gaming rules
Rules the agent must follow so it cannot cheat the exit condition.
  • Do not modify the check command or exit criteria to force success
  • Do not skip, disable, or bypass checks to pass the exit condition
  • If stuck after several iterations, stop and report blockers instead of gaming metrics
How to run this loop
Includes install files
Run “CI Failure Watcher” in your agent
Deeplinks and “Open in Cursor” only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

  • Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace between passes.
  • Install files — optional hooks under .cursor/ or .claude/ that fire on events (save, commit, etc.). You must download and extract these into your repo.
  1. 1

    Download and extract install files

    Click Install files on this loop, unzip, and merge into your project root so paths like .cursor/loops/ci-failure-watcher/watch.sh exist on disk.

    Restart Cursor or reload the Claude Code session so hooks are picked up. Until then, nothing is “installed” — the browser cannot write into your repo.

  2. 2

    Copy or open the kickoff prompt

    Use Use loop to copy the kickoff, or Open in Cursor / Open in Claude Code to pre-fill the prompt in that app. Those links only carry text, not hook files.

  3. 3

    Paste and let the agent self-pace

    Paste the kickoff into agent chat. The agent should run your check command between iterations and stop when the exit condition passes.

Full guide with Cursor /loop notes: How to install loops

interval trigger
CI
Every 5m
Check CI status
Investigate failure
Verify locally
Latest CI run conclusion is success
Rendering diagram…
Steps
What the agent does on each pass.

1. Check CI status

Check the latest CI run for the current branch using gh CLI.

gh run list --branch $(git branch --show-current) --limit 1

2. Investigate failure

If CI failed, read logs, identify the root cause, and apply the smallest fix.

3. Verify locally

Run the failing CI step locally before pushing again.

Kickoff prompt
Copy this into your coding agent to start the loop.
/loop 5m Start the "CI Failure Watcher" loop.

Goal: latest CI run on this branch is green.
Max iterations: 12.
Between iterations run: gh run list --branch $(git branch --show-current) --limit 1
Exit when: latest run conclusion is success.

Step 1: Check CI status. If failed, read logs, fix root cause, verify locally, and push if needed.

Related loops

CI
manual
3.4k2k
Implement on a branch, run tests, push, open a PR, wait for CI, and loop until checks pass and the PR is ready to merge.

Start the "Ship PR Until Green" loop. Goal: PR is open with all CI checks passing Max iterations: 10 Between iterations run: gh pr checks Exit when: all PR checks are success Step 1: Implement the change, test locally, push, open PR, and fix CI until green. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Claude CodeCursorCodex
pr
ci
ship
continuous-claude
by loops!
View
DevOps
interval
1.4k1.9k
On an interval, hit health and smoke endpoints after a deploy until all checks return healthy responses.

/loop 15m Start the "Deploy Verification Loop". Goal: all post-deploy health and smoke endpoints return success. Max iterations: 8. Between iterations run: curl -fsS <your-health-url> Exit when: every configured endpoint succeeds. Step 1: Hit health/smoke URLs. If any fail, inspect deploy logs and fix or escalate.

CodexCursorClaude Code
deploy
devops
smoke-test
by loops!
View
Testing
manual
Hardened
1.8k1.3k
Run your test suite, fix the smallest root cause on failure, and repeat until every test passes.

Start the "Test Until Green" loop. Goal: all tests pass Max iterations: 10 Between iterations run: npm test Exit when: tests exit 0 Step 1: Run tests. If there are failures, fix the smallest root cause, then repeat. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

CursorClaude Code
testing
tdd
ci
by loops!
View