verification-before-completion

To verify code quality before claiming task completion, you must execute relevant commands like test suites or linters and review their output. This ensures concrete evidence precedes any success assertions, preventing false claims of passing tests or clean code.

Developers make false claims about bug fixes when declaring completion without fresh verification evidence. Assuming a fix works without executing test suites or validating command output leads to shipping broken work and premature status updates.

The best way to enforce test verification before a pull request is applying an evidence before claims principle. This requires running the test suite, confirming zero failures, and validating linter output before stating all tests pass or code is clean.

You need to run verification commands during software development at any stage where status updates or assertions are made. This mandates executing relevant commands and validating their output before declaring tasks complete, bug fixes successful, or tests passing.

Verification before completion works without external dependencies. It enforces a strict process requiring execution of relevant commands and validation of their output to confirm status, relying on no specific testing frameworks or external libraries.

The limitation of enforcing evidence before claims in code quality is that it only mandates running commands and reviewing output before assertions. It does not execute the commands itself or validate the correctness of the specific tests written.