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

loops!
BrowseSign in

Browse loops

Search 42 loops by name, tag, category, or agent. Copy the kickoff and let your agent self-pace until the exit condition is met.

42 loops

Showing 19 of 42 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
Testing
event
Hardened
2.2k1.9k
Hook that runs tests before git commit commands to block commits when the suite is red.

Install and run the "Pre-Commit Guard" loop. Goal: block git commits when tests are failing. Between iterations run: npm test Exit when: tests exit 0 before each commit. Step 1: Before any git commit, run tests. Fix failures before committing.

CursorClaude Code
hooks
testing
git
pre-commit
by loops!
View
Automation
manual
2.4k1.7k
When a check fails twice the same way, append a guardrail sign to .ralph/guardrails.md so the next iteration avoids repeating it.

Start the "Guardrails Learning Loop" loop. Goal: tests and lint pass without repeating prior failure patterns Max iterations: 12 Between iterations run: npm test && npm run lint Exit when: all checks pass Step 1: Read .ralph/guardrails.md, run checks, and if a failure repeats, add a sign before fixing. 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 CodeCodex
ralph
guardrails
learning
by loops!
View
Testing
manual
Hardened
2k1.1k
Run failing tests repeatedly, classify each failure as flaky or real, and fix only confirmed regressions.

Start the "Flaky Test Triage" loop. Goal: classify failing tests as flaky vs real and fix only real regressions Max iterations: 5 Between iterations run: npm test -- --testPathPattern=<failing-suite> Exit when: every failure is classified and real regressions are fixed or explicitly deferred Step 1: Run the failing suite multiple times. Classify each failure, fix real ones, and document flaky behavior. 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 CodeCursor
testing
flaky
triage
by loops!
View
Maintenance
manual
1.7k1.2k
After code changes, find affected docs and update README, API references, and inline comments to match.

Start the "Docs Sync After Edits" loop. Goal: documentation matches the current code changes Max iterations: 3 Between iterations run: git diff main...HEAD --name-only Exit when: all affected docs are updated and verified Step 1: Review the diff, find stale docs, update them, and verify accuracy. 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.

Cursor
docs
maintenance
sync
by loops!
View
Security
manual
1.9k1.8k
Fix high/critical npm audit findings one at a time with test verification — not a blind npm audit fix --force.

Start the "npm Audit Fix Loop" loop. Goal: no high or critical npm audit vulnerabilities Max iterations: 10 Between iterations run: npm audit --audit-level=high && npm test Exit when: npm audit reports no high/critical issues Step 1: Pick one high/critical advisory, apply the safest fix, run tests, and 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
security
npm
audit
by loops!
View
Quality
manual
2k1.5k
Run automated accessibility checks on changed routes, fix violations, and repeat until the audit is clean.

Start the "A11y Audit Until Clean" loop. Goal: zero serious accessibility violations on changed UI Max iterations: 8 Between iterations run: npm run test:a11y Exit when: a11y audit exits 0 Step 1: Run the a11y audit on changed routes. Fix each violation, prioritizing keyboard and screen reader issues. 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
a11y
quality
frontend
by loops!
View
Testing
manual
Hardened
1.4k1.7k
When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implementer's rationale.

Start the "Independent Verifier Pass" loop. Goal: build, lint, and tests pass under independent verification Max iterations: 8 Between iterations run: npm run build && npm run lint && npm test Exit when: all verifier commands exit 0 Step 1: Run build, lint, and tests as a verifier. Trust only command output, not prior claims. 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 CodeCursor
verification
testing
letitloop
by loops!
View
Testing
event
Hardened
1.5k1.3k
Hook-based loop that runs related tests after file edits to catch regressions early.

Install and run the "Post-Edit Test Guard" loop. Goal: after each batch of file edits, related tests must pass before continuing. Between iterations run: npm test -- --findRelatedTests <edited files> Exit when: related tests exit 0. Step 1: After edits, run related tests. If they fail, fix before making more changes.

CursorClaude Code
hooks
testing
regression
by loops!
View

Page 1 of 5