maintain-verify-skilllisted
Install: claude install-skill SeanoChang/seanock
# maintain-verify-skill
A verify skill is written once, and the app goes on changing. A file moves,
a command gets a new flag, a feature is added with no entry in the map. Then
a pass covers less than it says. This skill finds those places.
The verify skill is the folder `.claude/skills/verify-<app>/` of the
project: the feature map `features.json`, the runner `verify`, and a short
skill file. The skill `create-verify-skill` wrote it.
## 1. Look
Run this from anywhere, as its own command, with no pipe:
```bash
python3 ~/.claude/skills/maintain-verify-skill/scripts/drift.py check --project <project root>
```
`check` starts the runner, so it builds the app and runs every step, each in
a fresh temp folder, as a verify run does. For a quick look, leave the run
out with `--no-run`. The paths, the runner copy, the form of the map and
the doctor of the runner are still checked, and nothing of the app runs.
For the doctor, the runner copy is started, only when it is the current
runner byte for byte and in Python's isolated mode, so no file of the
project is loaded as code:
```bash
python3 ~/.claude/skills/maintain-verify-skill/scripts/drift.py check --project <project root> --no-run
```
When the project has two verify skills, add `--app <name>`.
Read the exit code and the last line together:
| Exit | Last line | Meaning |
| --- | --- | --- |
| 0 | `drift: clean` | The skill fits the project. |
| 1 | `drift: summary stale=N uncovered=N failed=N` | One finding on each line ab