In the video I showed you my 3 favorites. As promised, here are all 15, pulled together by Matt van Horn and copied here in full, with the copy-paste command for every single one.
This whole list comes from Matt van Horn, who compiled the top 15 AI loops from across the internet. You can check it out here on X → — go give him a follow. I’ve dropped the full list below so you have every one in a single place.
First, What A Loop Even Is
A loop is just one idea: deciding when and how long your agent keeps working. Normally you ask, it answers once, done. A loop lets it keep going, checking its own progress, so instead of one reply it can work for minutes or even hours toward a finish line.
Each loop below is tagged with the command that powers it, so here’s the quick key:
Goal
Keeps working until the outcome is achieved.
Loop
Repeats a task while you’re watching.
Schedule
Runs while you’re gone, laptop closed.
A few entries are tagged differently, a harness (a template you clone), a routine (a scheduled job), or a shipped tool (something you install). Now here are all 15.
Loop 1 · loop
The Build-Test-Fix Pair
The single most-demoed loop in the whole pull, from a creator named raycfu whose walkthrough did 43,587 views and 1,040 comments on Instagram. Two agents: a builder that writes code and a checker that runs the tests, types, and lint and reports exactly what broke. They pass work back and forth until it is clean. The whole pitch is the pain it kills: a one-shot agent ships its bugs.
/loop build the next item on the plan, then run tests, typecheck, and lint. Feed every failure back as the next instruction and fix it. Stop when the build is green and the checker has nothing left to report.
Loop 2 · loop
Boris’s Verifier Loop
This is the loop in Boris Cherny’s own words, and the highest-engagement description of it (@bcherny, 781 likes): run Claude Code plus an advanced model plus a verifier in a loop, feed it tasks, and remove bottlenecks as you go. The verifier is the part everyone skips. Without it you are just trusting the agent.
/loop work the task list. After each task, have a separate verifier model check the result against the spec and the tests. Only move on when it passes. Surface anything the verifier rejects twice.
Loop 3 · harness
The Loop-Engineer Starter
The most-watched actually-set-one-up video, from AI Jason (15,436 views, 537 likes), ships a free loop-engineer template: a codebase harness plus a knowledge template you clone, point at your repo, and run, so you are not wiring the build, observe, verify, and stop scaffolding from scratch. The fastest on-ramp if you want a loop running tonight without designing the plumbing yourself.
git clone https://github.com/JayZeeDesign/loop-engineer-template
Loop 4 · loop
The Five-Minute Repository Maintainer
Peter Steinberger, who merged 859 PRs across his repos in the last 30 days at a 95 percent acceptance rate, runs this one on a tight timer: every five minutes while he is working, the agent does one small, verified piece of upkeep. What to clean is the agent’s call, not a hardcoded script. That decision is the whole point.
/loop 5m make one small verified repository improvement: a flaky test, a stale comment, a missing type. One change, one commit, tests green. Never touch anything risky.
Loop 5 · goal
The Plan-Generate-Verify-Fix Loop
A creator named qbuilder (4,560 views, 125 likes on TikTok) runs a bounded version that fixes the runaway problem cold: plan, generate, verify, fix, repeat, with everything saved to files and a hard cap of five iterations. You only read the final version. The cap is what makes it safe to leave.
/goal plan the task, implement it, verify against the tests, and fix what failed. Save state to files each pass. Max 5 iterations. Stop at the first clean pass or when the cap is hit, and tell me which.
Loop 6 · shipped tool
roborev, The Post-Commit Reviewer
roborev is a free, open-source code-review tool (a Go binary; install from roborev.io) that surfaced in the research through Dan Kornas. It installs a git hook so every commit triggers a background review, then feeds the findings into an agentic fix loop while the context is still warm. The launch tweet was quiet at 20 likes, but the repo is the real signal: 1,410 stars and commits shipping the same day I write this. It is the installable version of the one thing this whole piece argues is the hard part, a verifier living inside the loop, and it plugs into Claude Code, Codex, and Gemini CLI.
roborev init # adds a post-commit hook: every commit triggers a review roborev fix # the agentic loop that fixes the surfaced findings
Loop 7 · goal
The Goal-Meta-Skill
The breakout skill of the month, surfaced by evgenii.arsentev (32 likes, 950 views) and sitting at 600-plus stars in days: a skill whose only job is to turn a vague ask into a rigorous goal, specifying the result, how to verify it, what not to touch, and when to stop. As he put it, your agent is not dumb, your instructions are just vague.
/goal before doing anything, rewrite my request into a precise goal: the exact end state, how you will verify it, what you must not touch, and the stop condition. Confirm that goal, then execute against it.
Loop 8 · routine
The 15,000-Emails-A-Day Loop
A builder on r/LangChain posted the full architecture for an email agent that processes 15,000 hotel guest emails a day: it loops the inbox, classifies and drafts, and escalates only what needs a human. It is the rare Reddit post that ships the whole production loop, not a demo.
/schedule every 15 minutes, pull new guest emails, classify each, and draft a reply for the routine ones. Queue anything sensitive for me and log every decision. Never auto-send a refund or a booking change.
Loop 9 · loop
The Anti-Spin Loop
The best-designed loop on Reddit, a Claude Code skill posted to r/claudeskills. It runs an autonomous build, audit, and verify cycle until a machine-checkable contract passes, with explicit anti-spin stops: no-progress detection, a retry cap, flip-flop detection, and a budget. It exists because, as the author puts it, most agent loops never stop to ask whether they are actually making progress, so they retry the same broken approach or quietly edit the test to pass.
/loop build toward the goal, then audit and verify against a machine-checkable contract. Stop if you make no progress, repeat an approach, flip-flop between approaches, or hit the budget. Finish only when the contract passes.
Loop 10 · routine
The Write-Loops-Not-Code Routine
The line that started all of this, from the man who built Claude Code: he does not write code anymore, he writes loops, and they write the code while he sleeps. The most-shared version (@0xMovez, 984 likes) puts a number on it: 30 percent of his code is now fully written by loops. The shape is a scheduled routine that watches your PRs and lands the fixable ones overnight.
/schedule every night, watch my open PRs. Auto-fix build failures, answer review comments in a fresh worktree, and rebase what is stale. Leave anything ambiguous for me. State in git so a crash loses nothing.
Loop 11 · loop
The Human-In-The-Loop Approval Queue
The most practical pattern from the no-code crowd, from a thread on r/n8n: the workflow runs, then pauses and sends you a message with approve, revise, or skip buttons, treating human review as its own queue with reminders and deadlines. Same loop shape, but the stop condition is your approval instead of a passing test.
/loop run the task, then pause and send me approve / revise / skip on Telegram before anything ships. On approve, continue. On revise, take my note and redo. On skip, move to the next item.
The rest of the truly copy-paste-ready loops live in Matthew Berman’s Forward Future Loop Library, a curated catalog where the vetting, not a like count, is the signal. These four earned a slot on usefulness alone.
Loop 12 · goal, catalog
The Production Error Sweep
Berman’s highest-utility goal. It reads your production logs, separates real actionable errors from noise, fixes the actionable ones with a test, and opens a PR. The value is the triage; tell it what “actionable” means or it chases ghosts.
/goal review the last 24h of production errors. For each one that is actionable and reproducible, write a fix with a regression test and open a PR. Ignore transient and third-party noise. Done when the actionable list is clear.
Loop 13 · goal, catalog
The Quality Streak Loop
Berman again, and the one that respects how flaky “it works” really is. It does not stop at the first green run; it tests realistic scenarios and only declares victory after a streak passes in a row. One green run is luck. A streak is reliability.
/goal run the full product test suite against realistic scenarios. Fix whatever fails, then run again. A new failure resets the count. Done only after 10 consecutive clean passes.
Loop 14 · shipped command, catalog
The Adversarial-Review Power Tool
Lukas Kucinski’s Clodex loop has Codex review Claude’s pull requests before merge, so two different model families have to agree before code lands. Paste it verbatim.
/clodex [task] think hard --max-iter 5 --threshold medium
The --max-iter 5 and --threshold medium are the whole point. It argues with itself up to five times and only passes work that clears the bar.
Loop 15 · shipped command, catalog
The Completion-Contract Power Tool
3goblack’s loop (@Dis_Trackted) fixes the most common failure: an agent that says “done” when it is not. Before any work starts it writes a contract of what “complete” means and what evidence proves each requirement, then refuses to claim success without that evidence.
$goal-planner-codex [task]
If you only steal three
Start with the build-test-fix pair (1) for anything with a clear pass or fail, the goal-meta-skill (7) to kill vague asks before they waste a run, and the human approval queue (11) for anything going out in your name. You can stack all three on one job.
Full credit for this roundup goes to Matt van Horn on X. Go follow him for the next one.
The Only AI Masterclass You Need
If this guide helped, but you’re looking to go deeper, I got you!! My 30-Day Challenge takes you from saving AI tips you never use to actually building with AI, step-by-step.
I show you exactly how I automated two e-commerce brands, my social media, and most of my personal life, then hand you the agents, workflows & systems to do the same. I’m teaching you every single thing I know with one lesson and one build a day.
Join the AI Masterclass →© 2026 Mariah Brunner. All rights reserved.