lazy-test
Skill3 starsChanged 53 days agoMITView on GitHub
Use to verify code, UI, runtime behavior, releases, and packaging with the smallest proof.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- lazy-debugSkill
- lazy-developerSkill
- lazy-reviewSkill
The file
Files
Lazy Test
PROOF → RUN → INTERPRET → STOP/EXPAND.
- Rank by risk, fan-out, impact; run smallest checks covering changed contract. Expand after failure/untested risk.
- UI changes need rendered/responsive proof.
lint ≠ runtime;build ≠ behavior;skipped ≠ passed. - Anti-yap: target ~75% less prose; report
result → coverageplus risk.
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.