agentleFS
sainzssainzs/santiagosainz-skills/skills/core/test-and-verify/SKILL.md

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

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
  1. Distinctive:

    Do one job: prove one behavior changed or still works.

    line 12
  2. Distinctive:

    Prefer the repo-native runner and the narrowest meaningful command.

    line 14
  3. Distinctive:

    After two identical failures, change approach instead of looping.

    line 16
  4. Distinctive:

    Use when changing behavior, fixing a bug with a known expectation, hardening a workflow, or proving an app can actually run.

    line 20
  5. Distinctive:

    Add a failing proof first when the behavior is testable and risk justifies it.

    line 35
  6. Distinctive:

    Run the original proof and any adjacent gate needed for confidence.

    line 38
  7. Distinctive:

    Test behavior through public interfaces.

    line 43
  8. Distinctive:

    Avoid mocks of internals unless the boundary is external, slow, costly, or nondeterministic.

    line 44
  9. Distinctive:

    Do not bulk-write imagined tests ahead of implementation.

    line 45
  10. Distinctive:

    Prefer one useful regression over many brittle assertions.

    line 46

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Existing failing test or check.
  2. New behavior test through a public interface.
  3. CLI/API/browser smoke repro.
  4. Build/type/lint gate for structural changes.
  5. Manual evidence only when automation is impractical.

Workflow

  1. Establish the baseline with the narrowest meaningful command.
  2. Add a failing proof first when the behavior is testable and risk justifies it.
  3. Make the smallest edit that satisfies the proof.
  4. Refactor only while green.
  5. Run the original proof and any adjacent gate needed for confidence.
  6. 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:

  1. Behavior proved.
  2. Files changed.
  3. Proof added or reused.
  4. Commands run and results.
  5. Residual risk.

Download now (ZIP)

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.