verification-before-completion

Enforce code verification by implementing a strict protocol that requires running specific commands and validating exit codes before any completion claims are made, ensuring evidence precedes assertions.

Evidence-based completion is a rigorous process requiring tangible command output and exit codes as proof of correctness, preventing premature claims of success and maintaining honesty in task completion.

Run test suites and linters before committing code to generate mandatory verification evidence, ensuring that if tests fail or linters report errors, the completion claim remains invalid until resolved and re-verified.

Prevent shipping incomplete code by applying mandatory process enforcement that blocks success assertions until all verification steps are executed and validated, addressing the risks of costly errors.

Verification commands are suitable for agentic task completion, satisfying the need for rigorous, repeatable verification steps to ensure automated processes validate work output before declaring success.