test-and-verify
Skill1 starsChanged 3 months agoMITView on GitHub
Test and verify one behavior through a tight evidence loop: baseline, failing proof when useful, minimal edit, and final proof. Use for tests, verification, TDD, regression-proofing, smoke checks, readiness validation, or prove-change.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- melconcoast/code-ideatheir own version, first seen Nov 2, 2026
- cellrishi-code/claude-skills-atlastheir own version, first seen Oct 4, 2026
- lucasrafaldini/paperdecktheir own version, first seen Sep 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- cellrishi-code/claude-skills-atlas★ 5same name
- melconcoast/code-idea★ 4same name
- lucasrafaldini/paperdeck★ 1same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- debugSkill
- domain-modelingSkill
- handoffSkill
- implementation-planSkill
- requirements-reviewSkill
- webgl-scroll-siteSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
10
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 12
Do one job: prove one behavior changed or still works.
- Distinctive: line 14
Prefer the repo-native runner and the narrowest meaningful command.
- Distinctive: line 16
After two identical failures, change approach instead of looping.
- Distinctive: line 20
Use when changing behavior, fixing a bug with a known expectation, hardening a workflow, or proving an app can actually run.
- Distinctive: line 35
Add a failing proof first when the behavior is testable and risk justifies it.
- Distinctive: line 38
Run the original proof and any adjacent gate needed for confidence.
- Distinctive: line 43
Test behavior through public interfaces.
- Distinctive: line 44
Avoid mocks of internals unless the boundary is external, slow, costly, or nondeterministic.
- Distinctive: line 45
Do not bulk-write imagined tests ahead of implementation.
- Distinctive: line 46
Prefer one useful regression over many brittle assertions.
“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.
Files
test-and-verify
Ship one behavior with evidence.
Unix/Pi Contract
- Do one job: prove one behavior changed or still works.
- Consume a target behavior and repo commands; emit changed files plus exact proof.
- Prefer the repo-native runner and the narrowest meaningful command.
- Act, then verify. Do not narrate every tool step.
- After two identical failures, change approach instead of looping.
Use
Use when changing behavior, fixing a bug with a known expectation, hardening a workflow, or proving an app can actually run.
Proof Ladder
Choose the first proof that gives real confidence:
- Existing failing test or check.
- New behavior test through a public interface.
- CLI/API/browser smoke repro.
- Build/type/lint gate for structural changes.
- Manual evidence only when automation is impractical.
Workflow
- Establish the baseline with the narrowest meaningful command.
- Add a failing proof first when the behavior is testable and risk justifies it.
- Make the smallest edit that satisfies the proof.
- Refactor only while green.
- Run the original proof and any adjacent gate needed for confidence.
- Report exact commands and outcomes.
Test Quality
- Test behavior through public interfaces.
- Avoid mocks of internals unless the boundary is external, slow, costly, or nondeterministic.
- Do not bulk-write imagined tests ahead of implementation.
- Prefer one useful regression over many brittle assertions.
Output
Return:
- Behavior proved.
- Files changed.
- Proof added or reused.
- Commands run and results.
- Residual 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.

