verification-before-completion

To verify code changes before claiming task completion, you must run relevant commands like linters and test suites, analyze their output, and confirm zero errors before asserting success. This prevents premature claims and undetected errors.

AI agents may falsely report a bug is fixed because they trust partial checks or assumptions. Enforcing a mandatory verification protocol requires executing test suites and analyzing their output before any completion claims are made, mitigating false positives.

A verification protocol in a CI/CD workflow is a strict process that mandates executing and analyzing relevant commands like builds and linters to gather evidence before assertions. It maintains development integrity by preventing false positives and undetected errors.

Yes, you can use automated verification to prevent false positives in builds. By mandating the execution and analysis of test suites and linters before declaring success, you mitigate risks associated with trusting agent reports or assumptions.

You enforce running linters and test suites before committing code by integrating a mandatory verification protocol. This protocol requires executing the commands, verifying their output, and confirming all checks passed with zero errors before completion is declared.