verification-before-completion

To enforce a verification process before claiming code completion, you must run specific verification commands and analyze their output to gather demonstrable proof. This prevents premature success assertions by ensuring all requirements are met through evidence.

The best way to prevent shipping incomplete or broken code is to mandate running tests, linters, or build commands before any commit or pull request. Reviewing the actual output prevents assumptions and ensures code quality through demonstrable proof.

Claiming a task is complete without verification causes regressions because it skips mandatory checks and relies on assumptions. Enforcing a strict verification protocol ensures that assertions of correctness are supported by analyzed command output, preventing costly errors.

To verify task success using command output analysis, run your designated verification commands and review the results. You must use this evidence to support any assertions of correctness, passing, or completion before finalizing the work.

You need to run verification commands before a pull request whenever you intend to claim work is complete. This mandatory step ensures you have analyzed the command output and gathered the proof required to assert that the code works and requirements are met.

Asserting code correctness without running linters or tests is not permitted under a strict verification protocol. You must execute verification commands and analyze their output to support any claims of success, preventing errors due to skipped checks.