verification-before-completion

To enforce verification before claiming code completion, identify and run specific command-line tools for testing, linting, and building. You must analyze their full output and exit codes to gather concrete evidence before making any assertions of success.

The best way to prevent premature claims of work completion is implementing a strict protocol that requires running verification commands and analyzing their output. This ensures evidence-based claims by demanding concrete exit codes as proof before any satisfaction is expressed.

To verify code quality before committing changes, run your unit tests and confirm they pass, check the linter output for errors, and ensure the build command exits with a status code of 0. Only claim success after reviewing this evidence.

Mandatory verification does not require specific testing tools or frameworks. It applies to any command-line tools you use for testing, linting, and building, requiring you to read their full output and verify exit codes before asserting completion.

Your development process needs a strict completion verification protocol to prevent costly errors and maintain honesty. It ensures all verification steps are performed with concrete output evidence before any claims of success or satisfaction are made.