verification-before-completion

To verify code correctness before completion, you must run fresh execution commands, such as test suites or linters, and review their output to ensure zero failures before making any success assertions.

Running fresh verification commands prevents false completion claims by ensuring your status report is backed by current evidence, avoiding the pitfall of trusting old test results or partial checks during development.

The best way to prevent false claims of passing tests is to mandate independent execution of your test suite and validate the command output showing zero failures before stating that all tests pass.

You enforce evidence before assertions by requiring fresh verification command outputs for building, testing, and linting stages before allowing any claims of work completion, correctness, or passing status.

Manual code review does not replace running verification commands, because independent execution of tests and linters is required to generate fresh evidence that validates all claims of correctness and passing status.

To confirm zero test failures before committing code, execute the relevant test suite, check the output for failures, and state your assertion by including the specific command used and its result.