loop-review
Skill0 starsChanged 5 months agoMITView on GitHub
Review a loop iteration as an independent checker before proof, commit, push, merge, deploy, or completion claims.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- microlinkhq/skillstheir own version, first seen Nov 1, 2026
- VioletScar-Hui/Build_Great_Looptheir own version, first seen Oct 9, 2026
- hyodotdev/openiaptheir own version, first seen Oct 9, 2026
- getlago/lago-fronttheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- hyodotdev/openiap★ 166same name
- getlago/lago-front★ 163same name
- microlinkhq/skills★ 4same name
- VioletScar-Hui/Build_Great_Loop★ 2same name
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 repository11 other files it gives its agents.
- loop-anythingSkill
- loop-dog-foodSkill
- loop-proveSkill
- loop-recordSkill
- loop-reviewSkill
- loop-triageSkill
- loop-anythingSkill
- loop-dog-foodSkill
- loop-proveSkill
- loop-recordSkill
- loop-triageSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
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 8
Use this skill after the maker role changes files and before the loop claims completion.
- Distinctive: line 39
If there is any blocking finding, stop the loop before proof.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Loop Review
Use this skill after the maker role changes files and before the loop claims completion.
Inputs
loop-state.mdloop-contract.md- Git diff or changed file list
- Commands already run
- Proof command selected during triage
Review Checklist
Report findings first, ordered by severity:
- scope drift beyond the active task
- missing or weak proof command
- unrecorded state changes
- credentials, tokens, private data, or secret-looking values
- destructive behavior without explicit approval
- claims that are not backed by command output
Output
Write:
- blocking findings
- non-blocking findings
- residual risk
- whether the loop may proceed to proof
If there is any blocking finding, stop the loop before proof.
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.