Loop directory

Collect external links from docs weekly, archive dead ones via Wayback Machine, open a PR with replacements and a report of unfixed links.

Run every 15 minutes to classify CI failures, fix clear regressions in a worktree with verification, and escalate infrastructure or security test failures.

Run ci-triage on failing CI, fix clear regressions in isolation, verify before push, and update state—up to 3 attempts per cluster.

Every 5m, scan open PRs for CI failures or review comments; propose minimal fixes on allowlisted ones via worktree, escalating after 3 attempts.

Implement one approved story from your backlog, pass all checks, and commit with the owner's identity when done.

Replace all v1Client calls with v2Client, verify tests pass and TypeScript compiles clean, stopping after 20 turns.

Work through incomplete stories from prd.json, implement and test each, mark passes=true when done, repeat until all stories ship.

Run static checks and git diff until both pass or hit a blocker after 6 attempts.

Run npm test on test/auth until it exits 0, with only src/auth files modified and no test changes.

Run a full review pass inline, apply validated blocking findings at their owning layer, re-run fresh until the gate clears or blockers plateau—capped at 3 rounds with escalation.

A recurring six-phase check (build, types, lint, tests with coverage, secret and debug-log grep, diff size) that prints one fixed-format report every fifteen minutes so you catch drift before the PR, not in review. It is strictly read-only: the loop reports, you decide what to fix. It exits when the tests pass and the report reads READY twice running, escalates instead of retrying when the same check fails three times, and stops after eight checks no matter what. Adapted from ECC's verification-loop skill (affaan-m/ECC, MIT), whose 'continuous mode' names the cadence but has no turn cap, exit, or failure path; all three are added here.

Two reviewers from different model families, each in a fresh context, must both pass an objective rubric before a PR is opened — the maker-checker split with real model diversity. Each failed round fixes only what was flagged and re-reviews with reviewers that have no memory of the last round, so nothing anchors on prior findings. Hard cap of three rounds, tests may never be edited to pass, and the loop ends by opening a PR rather than pushing. Adapted from ECC's /santa-loop (affaan-m/ECC, MIT), which auto-pushes on agreement and has no verifiable exit; this version adds the test-exit condition and the human merge gate.

The generic persistent-task Ralph pattern: iterate on one named task until its acceptance criteria are met and the suite is green, bounded by a 15-turn cap and a no-progress stop. Anti-reward-hacking clauses keep it from editing tests to go green, and it hands off via a PR instead of merging. Swap the check command for your stack's.

Build and test a new /users/:id/avatar route until it passes tests, lint, and matches the OpenAPI schema.

Work through each task in .toh/plan.md, fix blockers, until the build command succeeds or you hit 40 turns.

Shape and execute infrastructure readiness objectives by gathering evidence, seeking approval at decision boundaries, then validating provisioning, configuration, and rollback in non-production before production deployment.

Refactor all files to TypeScript and run tests until the full suite passes.

Refactor src/api/ to use dependency injection, keep all existing tests passing, add tests for the new DI container, and output completion promise when done.

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

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

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.

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.

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.

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.

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.

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

Refactor the authentication module iteratively until all tests pass, stopping after ten attempts.