verify

Turn "it looks done" into a verdict backed by evidence.

Most verification passes fail in one of two directions: they trust the implementation and miss real defects, or they generate a pile of plausible-sounding problems that waste an hour. This skill is built against both.

All paths below are relative to this skill's directory.

Three laws

1. No verdict without an executed command. Every claim about the state of the code cites a command, its exit code, and a line of its output. A gate that could not run is reported as not run, never as passing.
2. No finding without a refutation attempt. Every candidate defect faces an independent skeptic whose job is to kill it. Survivors get reported; the rest are counted, not shown.
3. No repair that only silences the checker. Skipping a test, adding @ts-ignore, widening to any, swallowing an error, editing CI, or rewriting the plan to match the code — the loop refuses these and escalates instead. Enforced deterministically by scripts/forbidden-repairs.mjs, not by good intentions.

Violating the letter of a law is violating its spirit.

Modes