Menu

Individual skill

proof

0upvotes

Chooses and implements the cheapest trustworthy test boundary for a behavior or invariant, including regression, property, contract, integration, and end-to-end tests. Use when adding tests, protecting a bug fix, or proving changed behavior without optimizing for coverage counts.

skills/proof/SKILL.md

Read pinned source

Source commit cfa78f744564cec2c5aaf0cbacbada58d79b9e59

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# proof: the right test at the right boundary

The skill is the boundary choice. A large unit suite can miss a broken
checkout; focused API tests can catch the actual boundary failure. Test
count is not the goal, **catching real regressions is**.

## When to use

- "add tests for the checkout flow"
- "we need regression coverage for that bug you fixed"
- "just add a regression test for this bug, leave the suite alone"

## When NOT to use
Back to top