fnl-verification
Installation
SKILL.md
Verification
A report is a claim. The diff and the test output you read yourself are the evidence.
Pairs with tdd and diagnosing-bugs from mattpocock/skills, which produce the red and green evidence this skill reads.
Choose the tests
- Run the targeted tests at checkpoints, not after every edit: those covering the changed code and its traced consumers, plus the project's lint and unit checks for those packages. Pick them from the diff (packages, test name patterns, the end-to-end suite only when the user-facing path changed). Say when no test covers the change; when that change alters runtime behavior, name the gap and propose a test rather than skip it.
- Run a full suite only when the owner asks. Gates and pull requests use targeted tests; CI runs the rest after an authorized push. When the change touches widely shared code whose consumers you cannot trace in full, propose a full suite and wait for the owner's yes.
- Keep local fixtures small (about 1,000 items) unless the owner asks for larger stages.
- Heavy jobs (container-backed suites, scale measurements, end-to-end runs) run one at a time per machine under an atomic
mkdirlock (fnl-delegate"Heavy jobs" points to the snippet; without it,until mkdir "$LOCK"; do sleep 15; done, then remove the lock when the job ends); light targeted runs may overlap. Keep the machine awake for long runs.
Read the evidence
- Read the output, not the exit code alone: count what ran, what skipped and what was filtered out. A skipped or partially green run is not a pass.
- Missing setup, a missing API or credential is not a behavioral pass: report it as blocked.
- Enabled configuration, a tool's DONE, a tick in a task list or a moved HEAD is not proof of behavior.
- For queries, reports, infrastructure changes and forecasts, a run that completed is not proof the result is right: see
fnl-coding-routerreferences/non-code-work.md.