213 published loops. Copy one, swap in your repo, run it.
Every Monday morning, run the dependency vulnerability audit, open one PR fixing what auto-fix can handle safely, and file issues for the rest.
/schedule every Monday at 8am, run `npm audit`, open a single PR applying only non-breaking fixes with tests passing, and file one issue per remaining high or critical advisory with its CVE link and affected paths
Turn the commit history since the last release tag into a human-readable, categorized CHANGELOG entry ready for the next version.
/goal CHANGELOG.md has a complete entry for the next release — read every commit since the last version tag, group changes into Added, Changed, Fixed, and Removed, write user-facing descriptions (not commit messages), link PR numbers, and flag anything that looks like a breaking change; stop after 5 turns
Run a secrets scanner over the working tree and drive the findings to zero: real secrets get flagged for rotation, false positives get baselined.
/goal `gitleaks detect --no-git` reports zero findings — for each finding, tell me whether it looks like a real credential (flag it for rotation and replace it with an env var lookup) or a false positive (add it to the baseline with a comment); never print the secret value itself; stop after 8 turns
Generate a contract test for every documented endpoint in the OpenAPI spec so the spec and the implementation can never silently drift.
/goal every path in openapi.yaml has a contract test asserting its status codes and response schema — add tests for one untested endpoint per turn, run the suite, and fix either the spec or the handler when they disagree (tell me which you chose); stop when all paths are covered or after 15 turns
Iteratively shrink a Docker image under a size target using multi-stage builds, smaller base images, and layer cleanup, verifying the container still boots each turn.
/goal `docker images` shows the app image under 300 MB — apply one slimming change per turn (multi-stage build, slimmer base image, prune build deps, consolidate layers), rebuild, and verify the container starts and passes its healthcheck before the next change; stop at the target or after 8 turns
Shrink the production JavaScript bundle under a hard budget by attacking the largest modules with code-splitting, lighter imports, and dead-weight removal.
/goal the main production bundle is under 250 KB gzipped — run the build with the bundle analyzer, address the single largest contributor each turn (code-split it, replace it with a lighter import, or drop it), and confirm the build and tests stay green; stop at the budget or after 10 turns
Instrument the test suite with query logging, find endpoints issuing N+1 queries, and fix them with eager loading or batching until the hot paths are clean.
/goal no endpoint in the integration test suite issues more than 10 SQL queries per request — enable query logging in the test environment, find the worst N+1 offender, fix it with eager loading or a batched query, verify the count dropped and tests still pass, then move to the next; stop after 12 turns
Walk through outdated dependencies one package per turn, upgrading, running the full check suite, and pinning back anything that breaks.
/goal `npm outdated` lists no minor or patch updates — upgrade exactly one package per turn, run tests, lint, and build after each, commit if green, and pin the previous version with a note in UPGRADE-BLOCKERS.md if it fails; stop after 20 turns
Hunt down unreferenced exports, unused files, and unreachable branches, deleting them in small verified steps until the analyzer reports clean.
/goal `npx knip` reports no unused files or exports — remove one cluster of dead code at a time, run the full test suite and typecheck after each removal, and revert any deletion that breaks them; stop after 15 turns
Compare environment config files and example templates every hour and report keys that exist in one environment but not the others.
/loop 60m diff the keys (not values) across .env.example, config/staging.yaml, and config/production.yaml; report any key present in one file but missing in another, and any key in .env.example that no code references anymore
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com → Run the benchmark suite every 30 minutes during active development and raise a flag the moment any benchmark slips more than 5 percent from baseline.
/loop 30m run `npm run bench`, compare each result to the baselines in bench/baseline.json, and if any benchmark regressed more than 5%, show me the numbers and the commits since the last clean run
Chip away at the oldest TODO comments in the codebase, one per pass: either resolve it properly or convert it into a tracked issue.
/loop 30m find the oldest TODO or FIXME comment in the codebase, and either implement it (with a test) if it takes under 50 changed lines, or open a GitHub issue capturing its context and delete the comment; report which TODO you handled; stop when none remain
Keep a stack of feature branches rebased in order as their parents merge, resolving trivial conflicts and flagging risky ones for a human.
/loop 15m for each branch listed in .rebase-train (in order), rebase it onto its updated parent, resolve only trivial conflicts (imports, formatting, lockfiles), run the test suite, and push with `--force-with-lease`; if a conflict touches logic, stop that branch and leave a summary comment on its PR instead
Every 30 minutes, pull the newest unresolved Sentry issues, match each stack trace to the code, and draft a root-cause note and suggested fix per issue.
/loop 30m list the newest unresolved Sentry issues for this project, and for each new one: locate the stack trace in the codebase, write a short root-cause hypothesis and suggested fix as a comment on the issue, and flag anything that looks like a regression from the last release
Watch CI runs on main every 20 minutes and quarantine any test that fails then passes on retry, filing an issue for each one it benches.
/loop 20m check the last CI runs on main with `gh run list`; if a test failed and then passed on retry, mark it skipped with a link to a new tracking issue you open via `gh issue create`, and report what you quarantined
A Ralph-style loop that writes its own rules: when a check fails the same way twice, the failure pattern gets appended to a guardrails file that every later iteration reads first.
/loop read .ralph/guardrails.md before doing anything, then run the full check suite and fix the first failure; if a check fails twice with the same error, append the failure pattern and a one-line rule for avoiding it to .ralph/guardrails.md before retrying; stop when all checks pass or after 15 turns
/loopnew
A loop wrapping a goal wrapping a review: every 30 minutes, drive all PR review comments to resolved via /review, 10 turns max per pass.
/loop 30m /goal all PR review comments resolved via /review, stop after 10 turns
/schedulenew
On every push to main, check whether changed code drifted from the docs in /docs and open a PR fixing anything out of date.
/schedule on every push to main, check whether the changed code drifted from the docs in /docs, and open a PR fixing anything out of date
/schedulenew
Every weekday at 9am, label new GitHub issues from the last 24 hours by area and priority and post a one-line summary on each.
/schedule every weekday at 9am, label new issues from the last 24h by area and priority, and post a one-line summary on each
/goalnew
Run the formatter, hand-fix anything it can't auto-fix, and repeat until git diff is empty.
/goal `npm run format` leaves no diff — run the formatter, hand-fix anything it can't auto-fix, repeat until `git diff` is empty
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com → /goalnew
Run migrations, fix schema or SQL errors, and repeat until prisma migrate status reports clean, capped at 6 turns.
/goal all database migrations apply cleanly — run them, fix schema or SQL errors, repeat until `npx prisma migrate status` is clean; stop after 6 turns
/goalnew
Review your recent diff for debug code, dead branches, and bad names, then fix with minimal edits until lint and tests pass.
/goal the recent diff is clean and convention-aligned — review it for debug code, dead branches, and bad names, fix with minimal edits until `npm run lint && npm test` passes; stop after 4 turns
/goalnew
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
/goalnew
Add focused tests for the least-covered files and re-measure each turn until coverage hits 80 percent or the turn cap.
/goal test coverage is at least 80% with all tests passing — add focused tests for the least-covered files, re-run coverage each turn, stop at the threshold or after 12 turns
/goalnew
Implement a change, open the PR with gh, then keep fixing CI failures until every check passes, all in one goal loop.
/goal a PR is open for this change and every CI check passes — implement it, test locally, push, open the PR with `gh pr create`, then keep fixing failures (re-check with `gh pr checks`) until green; stop after 10 turns
/goalnew
Sweep a codebase from a legacy API to its v2 replacement with tests and typecheck as the safety net, capped at 30 turns.
/goal every file importing from `./legacy-api` now imports from `./v2-api`, all tests pass, and `npm run typecheck` is clean — stop after 30 turns
/goalnew
Drive a feature to done against explicit acceptance criteria: a working paginated endpoint, passing tests, clean lint, and a hard turn cap.
/goal the /users endpoint returns 200 with a paginated JSON body, all tests pass, and lint is clean — stop after 20 turns
/goalnew
The classic one-liner goal loop: iterate until every test passes and the linter reports zero problems.
/goal all tests pass and lint is clean
/loopnew
Poll gh pr checks every 10 minutes and get told when the PR is ready to merge, or a summary of which checks failed and why.
/loop 10m run `gh pr checks 1234`; if all pass, tell me it's ready to merge; if any fail, summarize which and why
/loopnew
Keep every PR labeled codex-watch healthy: fix CI failures, rebase behind-main branches, and nudge pending reviewers on a 15-minute cadence.
/loop 15m check every open PR labeled `codex-watch` and keep each healthy: fix CI failures, rebase when behind main, and nudge if a review is pending
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com →