prove-change
Installation
SKILL.md
The implementer checking its own branch against the spec agrees with itself.
This skill hands the branch to two provers that did not write it: a spec prover that walks the spec, and a bug prover that attacks the diff.
Each keeps a finding only when a test or driver it wrote fails at the branch HEAD, and this skill reruns every proof before it believes one.
It reports and hands the surviving proofs to your working tree; it fixes nothing.
Arguments: the spec's path, then an optional fixed point.
Steps
- Pin the branch.
The fixed point defaults to the merge-base of
HEADand the default branch; pass one when the default branch already holds the branch, as on a replay. Resolve both withgit rev-parse --verify <ref>^{commit}and stop if either fails, or ifgit log <fixed-point>..HEADis empty. The provers see committed work only: name any uncommitted change in the report, and do not prove it. Stop ifgit check-ignore -q .scratch/fails: the provers' worktrees go there and must stay out of your tree's status. Stop if the spec has no## Behavioursection with numbered entries.