Loop directory

Implement spec.md with test-driven development, loop until all tests pass and output COMPLETE.

Run a task until its probe passes, exhausting reasonable attempts before reporting blocked or complete.

Run the test suite repeatedly, fixing InterpreterMatchingServiceTests failures until all pass.

Implement each unchecked TODO item, run tests until they pass, then check it off; stop when the list is empty.

Update checkout docs and stop when the docs build succeeds or reaches 20 attempts.

Community loop loop for planning, sourced from submission. Verified exit condition, evaluator-gated.

Community loop loop for docs, sourced from submission. Verified exit condition, evaluator-gated.

Community loop loop for security, sourced from submission. Verified exit condition, evaluator-gated.

Community loop loop for automation, sourced from submission. Verified exit condition, evaluator-gated.

Community loop loop for testing, sourced from github. Verified exit condition, evaluator-gated.

Community goal loop for testing, sourced from github. Verified exit condition, evaluator-gated.

Run verify commands and benchmark checks until the target code scores 90 or higher on the benchmark, stopping after 5 attempts.

Community goal loop for devops, sourced from github. Verified exit condition, evaluator-gated.

Run tests and update changelog until both pass without altering the public API.

A cron-fired skill that finds its own work (failed CI, new issues, recent commits), fans each finding out to an isolated worktree, gates every fix behind an adversarial reviewer that assumes the code is broken, and leaves draft PRs — merging stays human.

A fill-in-the-brackets charter that turns any pile of small tasks into a self-checking loop: where the work is, how to check each item with evidence, a needs-me escalation list, a state file, and a per-run stop.

The four-settings loop template: a separate verifier model that never shares context with the writer, a hard stop rule, a state file re-read each cycle, and worktree isolation. Point it at a checkable backlog and let it run overnight.

Split a large mechanical job into 2–5 independent Codex lanes, each isolated in its own worktree with a frozen acceptance bar and binding judge, then block the final merge behind a full integration judge.

praetor is a Claude Code plugin that runs a plan → freeze acceptance bar → dispatch → independent fresh-context judge → resolve loop. Claude plans and judges, Codex executes; a FAIL from the judge cannot be overridden, with at most 2 retries before a loud takeover.

Run an agent repeatedly on a single refactoring task, persisting filesystem state between iterations until tests pass.

Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.

Run your static analyzer on the security ruleset, fix one high-severity finding at a time, re-verify, and loop until zero remain or 10 turns pass.

Pick the oldest untriaged issue, validate it against the current build, then label it, close if obsolete, or document repro steps—one per turn until the queue empties or 12 iterations pass.

Every Friday at 2pm, draft release notes from merged PRs into releases/DRAFT.md and verify all links resolve.

Query the catalog for unindexed foreign keys, create a migration per missing index, and verify each with a full test run until all FKs are covered or 6 turns complete.

Every night at 3am, dump the production schema and diff it against migrations, filing issues for any drift found.

Pull the slowest PostgreSQL statement, optimize its query plan with an index or rewrite, verify the improvement, and repeat until all captured queries run under 100ms or hit eight iterations.

Re-invoke a specific PR review skill every 20 minutes until the review completes or you stop it.

Execute work from PLAN.md until npm run lint and npm run test:e2e pass, scoping changes per AGENTS.md.

Build the feature from docs/spec.md and iterate until your test suite passes completely.