verification-before-completion

To prevent premature completion claims, enforce an evidence before assertions protocol requiring developers to run specific verification commands and analyze their output before stating any bug fixes or tests are passing.

Running verification commands before stating tests are passing is required to identify red flag rationalizations that bypass verification. This mandatory process backs all success claims with fresh, executed output, ensuring accuracy in development workflows and preventing false assertions.

The best way to verify bug fixes before creating a pull request is to run the defined test suite, analyze the output for failures, and only then claim the changes are complete and passing. This strict verification protocol ensures honesty and accuracy in development workflows.

Yes, the verification before completion approach applies to all stages including testing, linting, building, and agent task completion. It mandates running specific verification commands for each stage and analyzing their output before any success claims are made to prevent premature assertions.

To identify red flag behaviors that bypass verification in software engineering, look for common rationalizations used to skip running fresh verification commands. Enforcing mandatory verification before making any success claims helps users recognize and avoid these premature assertion behaviors.

Yes, you can use this verification protocol for agent task completion checks. It enforces running specific verification commands and analyzing their output before any success claims are made, ensuring agent tasks are evaluated for accuracy and preventing premature assertions across all development stages.