verify
The running half of the verdict: prove what the change does, before and after.
S=<this skill's directory>/scripts; <base> is the PR's base branch.
Prove a change
- Pick the proof from the record's proof contract:
- a bug fix: the check that fails on the old code;
- a feature: the flow on the real surface;
- a refactor: the full test suite.
Take the commands from the app's
verify-<app>skill when there is one.
- Run both sides:
bash "$S/both.sh" --base <base> --out <record>/proof/verify.json -- <command>.- Each side runs in a clean temporary worktree, so include the install step (
-- sh -c 'npm ci && npm test'). - A check the change adds is missing on the parent: pass
--from-head <test file>to run it against the old code. A parent failing on a missing file proves nothing.
- Each side runs in a clean temporary worktree, so include the install step (
- Read the outcome against the work type:
| Outcome | Bug fix | Feature | Refactor |
|---|---|---|---|
fixed (parent fails, head passes) |
proved | proved when the check is new | wrong: behavior changed |
same-pass |
not proved: the check does not catch the bug | fine for an old check; add the new one | proved |
regressed or same-fail |
blocks | blocks | blocks |
- UI: a screenshot pair (parent, head), same viewport and data, saved beside the manifest.
- Attach:
- in a rig:
rig proof add --artifact-type qawithPASSorBLOCKING,--candidate-sha <head sha>, and the outcome line as the money evidence; - outside a rig: the workbench record's
proof add. Cite logs by their manifest sha256.
- in a rig:
- Report: outcome, both exit codes, the manifest path, what was not run.
verify- skills
- New:
node "$S/new-verify-app.cjs" <app> --repo <app repo> --out <skills dir>reads the package.json scripts, Makefile targets and compose file into a command table, stampedverified: <date> at <sha>. Run each command once; fix any that fail before relying on it. - Upkeep:
node "$S/stale.cjs" <skill dir> --repo <app repo> [--days 14]exits 1 when the stamp is old or a listed command no longer exists. Report why; re-verify before refreshing the stamp.
Rules
- Evidence or nothing: a claim without a manifest, log or screenshot is not a verdict.
- Same command on both sides.
- Never fix the change. A failure is a finding for the author.
