Check that the work is really done before committing. Runs the project's test command and pipes its output to evidence-referee done, so the verdict comes from the evidence and not from a summary.
Installs into .claude/skills of the current project.
Are you the author of Verify?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ismaildasci-verify)
---
name: verify
description: Check that the work is really done before committing. Runs the project's test command and pipes its output to evidence-referee done, so the verdict comes from the evidence and not from a summary.
allowed-tools: Bash
---
# verify
Run this right before committing code changes.
1. Run the project's check command and pipe all of its output, including stderr and the exit code, to the referee. Replace `npm test` with the project's own command (for example `cargo nextest run`, `pytest`, `go test ./...`). The exit code line keeps the real status and lets a runner the referee does not recognise still count:
```bash
{ npm test; echo "exit code: $?"; } 2>&1 | npx evidence-referee done --criteria "all tests pass" --evidence - --fail-on missing,unsure
```
Until the package is on npm (early October 2026), `npx evidence-referee` fails with a 404. If it does, use `evidence-referee` instead of `npx evidence-referee` when the user has the alias from the README install note.
2. Read only the one-line JSON it prints.
- `met`: commit.
- `missing` or `unsure`: do not commit. Follow `next_step`, fix the cause, and run step 1 again.
- No JSON line (an npx 404, a missing key, a crash): there is no verdict. Do not retry in a loop and do not claim success. Tell the user the check could not run and why.
3. Do not paraphrase the test output to claim success. The verdict line is the evidence.
