verification-before-completion

To enforce running tests before declaring code completion, you need a verification workflow that mandates executing test suites and reviewing their outputs. This ensures concrete evidence precedes any claims of successful completion or bug fixes.

Preventing false positives when fixing bugs requires re-testing the original symptom and confirming resolution before claiming success. A verification protocol ensures you review concrete evidence from test runs rather than making premature assertions.

To verify a build process before claiming code is ready, you must execute specific verification commands like linters or build tools and review their outputs. This ensures all checks pass before making any status assertions.

Declaring code complete without evidence causes regressions because unverified changes may introduce hidden failures. Mandating the execution and review of test suites prevents shipping broken code by requiring proof of passing statuses.

Creating a workflow that requires passing linters before committing code involves enforcing a protocol where verification commands run and outputs are reviewed. This guarantees code quality by blocking success claims until checks pass.

You need strict verification in software development workflows whenever you commit code, fix bugs, or declare features passing. It mandates running test suites and build processes to ensure evidence precedes any success claims.