loops
Skill0 starsChanged 3 months agoMITView on GitHub
Run bounded improve-verify loops on any deliverable. Use after every critique that finds issues, whenever iterating toward a quality bar, when the user says iterate, improve, fix, try again, or not good enough — any time work cycles more than once. Set the budget BEFORE the first iteration.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- sophonfinance-wq/finance-automation-portfoliotheir own version, first seen Nov 1, 2026
- anlmalabs/skillstheir own version, first seen Oct 25, 2026
- 5dive-ai/skillstheir own version, first seen Oct 5, 2026
- xmeir-dev/skillstheir own version, first seen Oct 4, 2026
- vivary-dev/vivarytheir own version, first seen Sep 27, 2026
- michielhdoteth/awesome-ai-agent-toolstheir own version, first seen Aug 24, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- jwangkun/loops★ 123same name
- michielhdoteth/awesome-ai-agent-tools★ 62same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- 0-CYBERDYNE-SYSTEMS-0/FFT_nano★ 4same name
- vivary-dev/vivary-cli★ 4same name
- weselben/RooForge★ 4same name
- 5dive-ai/skills★ 2same name
- miketromba/skills★ 2same name
- thepictishbeast/claude-tools★ 1same name
- vivary-dev/vivary★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- cleanupSkill
- context-managementSkill
- critiqueSkill
- debuggingSkill
- design-decisionsSkill
- diff-managementSkill
- fan-outSkill
- final-checkSkill
- handoverSkill
- memorySkill
- orientSkill
- planningSkill
- researchSkill
- roadmapSkill
- verificationSkill
- web-testingSkill
- writing-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Set the budget: Default: 3 iterations. Complex/high-stakes work: 5.
- Distinctive: line 21
Check convergence: is the remaining-issues list strictly shrinking?
- Distinctive: line 27
Budget spent, still failing: STOP. Report to the user: what was attempted each iteration, what still fails, your best hypothesis why, and …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Loops
A loop = execute → verify → critique → fix. Loops are how quality happens; unbounded loops are how sessions die. Every loop needs a budget and an exit condition BEFORE it starts.
Setup (before iterating)
- Define done. The exit condition must be objective: tests green, checklist satisfied, critic approves. "Feels good" is not an exit condition.
- Set the budget. Default: 3 iterations. Complex/high-stakes work: 5. Write the budget down.
- Pick the verifier. Automated check > fresh subagent critic > self-review, in that order of preference.
Each iteration
- Fix ONLY what the last critique/verification flagged. No opportunistic extras — those go to the task list as separate items.
- Re-run the SAME verification. Changing the test mid-loop invalidates the loop.
- Log one line per iteration:
Loop N: fixed X, Y | remaining: Z. This log goes in the handover if the session ends mid-loop. - Check convergence: is the remaining-issues list strictly shrinking?
Exit rules
- Converged: exit condition met → proceed to ship phase.
- Failing for non-obvious reasons: switch to the debugging skill — hypothesis-driven, not blind re-fixing.
- Budget spent, still failing: STOP. Report to the user: what was attempted each iteration, what still fails, your best hypothesis why, and 2–3 options. Never silently accept failure; never loop past budget.
- Diverging (new issues appearing faster than fixes, or the same issue reappearing): stop immediately even with budget left — the approach is wrong. Re-plan; record a design decision about the abandoned approach and why it failed.
- Oscillating (fix A breaks B, fix B breaks A): stop, the two constraints conflict. Surface the conflict as a design decision for the user.
Anti-patterns
- Polishing beyond the exit condition ("one more pass") — done is done.
- Widening scope mid-loop.
- Re-verifying with a weaker check than the one that failed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

