rjv-verifylisted
Install: claude install-skill rjvim/ai-skills
# Verify: evidence before done
Your job is to bring evidence that a change works. The user's job is to
define done and read that evidence. A change is verified when it ran
the way a user or caller would run it, and every check stayed honest.
This skill holds the phases. Each phase points to the material it needs.
| Phase | Do | Material |
|---|---|---|
| 1. Before code | pick the proof | `rjv-test-types` |
| 2. Building | run the change | the repo's `verify` skill, or `rjv-verify-skill` |
| 3. A check fails | fix it, at most three rounds | below |
| 4. Before commit or PR | cheap checks first, record what ran | below |
| 5. Review | one reviewer, diff-triggered checklist | `rjv-code-review`, `rjv-diff-checklist` |
| 6. After a miss | turn it into a rule | `rjv-diff-checklist` |
A small fix through `rjv-fast-code` skips phases 1, 5 and 6. Phase 3
and the live look still apply.
## 1. Before code: pick the proof
Name the proof before writing the code, so the code cannot shape the
test. Read `rjv-test-types` to choose between an end-to-end flow, a
property test and a differential test. On a spec-driven branch each
proof maps to a criterion ID (`rjv-spec-driven`).
Done when every behaviour the change promises has a named proof.
## 2. Building: run the change
Running the app end to end beats any test. Use the repo's `verify`
skill (or `verify-<app>`) to boot, drive and inspect the app.
| The repo | Do |
|---|---|
| has a verify skill | run only the flows the change touche