verification-before-completion

To prevent unverified claims before declaring a software build complete, execute full verification commands like tests and lint checks, parse their outputs, and report evidence-backed results demonstrating success.

Evidence-based verification in CI-CD workflows is the process of running tests, builds, and lint checks end-to-end to gate completion claims with demonstrable, fresh output results rather than assumptions.

To enforce verification before merging a PR, apply a structured flow by identifying required checks, running them, reading outputs, verifying results, and only then claiming completion with fresh evidence.

Yes, this verification approach works with lint checks and builds by requiring you to execute these full commands end-to-end and provide their fresh output as the basis for any completion claim.

You should run verification commands end-to-end before claiming task completion to enforce honest status reporting and prevent premature success statements that lack demonstrable, fresh evidence from tests or builds.

Claiming completion without fresh verification evidence risks reporting unverified or premature success states, bypassing the required parsing of test, build, and lint outputs needed to gate PR reviews accurately.