verification-before-completion

To enforce evidence-based work completion claims, you must run verification commands and confirm their output before making any success assertions. This ensures accuracy and maintains honesty by preventing false claims of completion or success in your development workflow.

Immediate verification is the process of running verification commands and confirming the output before stating that work is complete. It prevents false completion claims by requiring concrete evidence immediately prior to making any success assertions.

To verify code changes before committing or creating a pull request, manually execute the relevant verification commands. You must confirm that all checks pass and provide the output evidence before making any claim of completion or success.

This verification process requires manual execution of verification commands. It does not run checks automatically; you must manually execute the commands and confirm the output to ensure all checks pass before making any completion claims.

You should require evidence before asserting software development tasks are finished to prevent false claims of completion or success. Enforcing immediate verification maintains honesty and integrity by ensuring all success claims are backed by concrete output evidence.