verification-before-completion

To prevent false claims of task completion in CI/CD, enforce a strict verification protocol requiring fresh execution of testing, linting, and building commands before reporting success status.

The evidence before assertions principle for code quality mandates executing verification commands and checking their outputs to confirm zero failures before claiming successful bug fixes, builds, or testing.

Verify bug fixing and testing success before committing code by running the relevant test suite, confirming the output shows zero failures, and avoiding rationalizations that lead to premature completion claims.

Common red flags when verifying task completion include making premature claims of passing tests or clean linters without backing them with executed verification commands and checking the actual output.

The verification protocol works with standard linting and building tools by enforcing mandatory verification across all development stages, requiring execution of specific commands before asserting success.

You should not use automated assertions for work status reporting without fresh verification command output, as skipping this step risks introducing regressions and making false claims about build or test completion.