Verify

Use when work is supposedly complete, before claiming it is done or merging. Checks the change against the acceptance criteria by running tests, typecheck, and review — and reports evidence, never bare assertions. Reads criteria from the Spine.From its SKILL.md

Install

npx -y skills add AndrewTtofi/spine --skill verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, as published. Nobody here has run it

verify — evidence before "done"

"Done" is a claim that requires proof. This skill produces the proof.

Steps

Read the acceptance criteria from journal.md and the commands from conventions.md.
Run the checks. Execute the test suite, typecheck, and build/lint commands. Capture the actual output.
Review the diff against conventions.md and the Spine's language: naming, module boundaries, dead code, missing tests.
Check each criterion off only with concrete evidence (a passing test, an observed behavior). Anything unverified stays open.
Report a short verdict: each criterion → met / not-met → the evidence. Quote real command output. If anything failed, say so plainly.
Write the result to journal.md. Do not mark the work complete in the Spine unless every criterion is met with evidence.

Spine I/O

Reads: journal.md (criteria), conventions.md (commands), context.md (language).
Writes: journal.md (verification result).

Notes

Never assert "tests pass" without showing the run. Evidence before assertions.
If a check can't be run, say why — don't skip silently.