verification-before-completion

Verification before completion requires running fresh evidence — tests, builds, linting, and type checks — then reading and interpreting their outputs to confirm your completion claim matches verified results, not assumptions.

Run your project's test suite, build process, linter, and type checker to generate fresh evidence. Read exit codes and output, confirm all pass, then declare completion only after interpreting those results against your claim.

Fresh verification prevents false positives and maintains trust. Running tests, builds, and linters before commits or pushes ensures your status claims reflect actual verified results, not prior assumptions.

No. The core principle is: no completion claims without fresh verification evidence. Visual inspection or prior success doesn't replace running tests, builds, linting, and type checks to generate current, concrete proof.

Valid evidence includes test execution results, build output and exit codes, linting reports, and type-checker output. All must be run fresh — not cached — and their results must be read and interpreted before you declare completion.

Before opening a pull request, run tests, build, lint, and type-check to generate fresh evidence. Verify all pass and results match your completion claim, then push only after that verification gate is satisfied.