verification-before-completion

To prevent premature declarations of fixed or passing code, enforce a strict verification protocol requiring fresh evidence from executed commands before making any success claims. This process mandates running tests, linters, and builds to validate assertions and prevent rework.

The evidence before claims principle requires developers to execute validation commands and read their output before asserting a task is complete. This mechanism maintains integrity by ensuring all completion claims are backed by verifiable test, linting, or build results.

To verify code completion before committing to CI/CD pipelines, identify and run the command that proves your claim, read its output, and verify success. You must run the test suite, linter, and build commands to confirm successful output and prevent regressions.

You need to run linter and test suite commands before declaring a task complete to reduce false positives and prevent the costly rework caused by shipping unverified code. This mandatory verification step prevents the introduction of regressions or broken builds.

The best way to enforce a verification process for code quality assertions is to apply a strict protocol across all development stages. This approach requires fresh evidence from executed commands to validate claims, preventing trust erosion and maintaining development integrity.

You should not skip a strict verification protocol before task completion in any development stage. Applying this process universally is necessary because skipping it risks trust erosion, increases false positives, and introduces regressions or broken builds into the codebase.