verify

A green build is not proof. It proves the compiler was satisfied. It does not prove the endpoint accepts the real payload, that the query returns the right rows, or that the change did not break the caller.

This skill trades that gap for receipts: recorded artifacts another person can re-run and reach the same verdict. No receipt, no pass.

Five gates, in order. Each gate ends on a receipt written to disk.

#	Gate	Question it answers	Receipt
1	Build	Does the changed code assemble?	command, exit code, tail of output
2	Static	Does it pass this repo's own syntax, type, lint, and schema checks?	per-tool exit code and finding counts
3	Clean code	Is this diff code you would approve?	finding per changed file, or explicit `none`
4	Scenario	Does each touched API behave live, across payload variants?	raw request and response per variant
5	Report	Would a colleague understand what you proved?	`report.md`

The three verdicts

Every gate lands on exactly one: