verification-before-completion

To enforce verification before code completion, you need a strict protocol that requires executing verification commands and analyzing their output before making any success claims. This prevents premature assertions by requiring fresh evidence from tests or linters.

Evidence-based assertion for code commits means concrete output from verification commands is required as proof before stating work is successful. It prevents dishonest status updates by ensuring all completion claims are backed by fresh, verifiable test results.

To stop premature success claims when fixing bugs, re-run the specific test that exposed the bug and confirm it passes. This verification protocol mandates analyzing command execution output before declaring the bug resolved.

No specific testing frameworks are required to verify work completion before PR submission. The protocol applies to any verification command execution and output analysis, ensuring evidence backs assertions across all task stages.

The limitation of enforcing a verification protocol before task completion is that it strictly requires running relevant commands every time a success claim is made. It cannot verify work if no appropriate verification commands or tests exist for the specific task.