agentleFS
oliwoodmanoliwoodman/verify-loop-skill/SKILL.md

verify-loop

Skill3 starsChanged 5 months agoNo licenceView on GitHub

Run a supervised, self-verifying loop on a coding task instead of hand-prompting each step. You give it a goal; it works one task at a time, and after every change it actually verifies the result — runs the app, clicks the flow, or runs the tests — with the check done from a fresh perspective so the agent isn't grading its own homework. Commits on green, tracks progress on disk, and stops itself on done / max iterations / repeated failure. MANDATORY TRIGGERS: 'verify loop', 'run verify-loop', 'loop on this', 'set up a loop for this'. STRONG TRIGGERS (use when tied to a real task): 'keep going until it works', 'build this and check it actually works', 'do this autonomously but safely', 'loop until the tests pass', 'work through this list and verify each one'. Built on the idea that the loop is the easy part — verification is the point.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. quocld/hephaestus-agent-skills★ 8same name
    2. qyndex/claude-init★ 2same name
    3. GerardoRdz96/claude-skills★ 0same 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.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.