verification-before-completion

Identify the command that proves your claim, run it fresh and completely, read the full output including exit codes, and only then state the result with that evidence. Never commit based on assumptions or previous runs.

Use the red-green cycle: write the test, confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

No, a linter passing does not prove compilation or build success. Linters check style and static issues but do not verify the code compiles or runs, so you must run the actual build command and check its exit code.

No, agent success reports must be independently verified. Check the version control diff to confirm actual changes were made and run the relevant verification commands yourself before reporting completion.

Never. The rule has no exceptions for small changes, tiredness, or confidence. Partial checks and assumptions prove nothing, so run the full verification command every time before any completion claim.