verification-before-completion

To verify code changes before completion, execute prescribed testing, linting, and build commands, read their full output with exit codes, and only declare success with fresh evidence.

A verification workflow in CI pipelines is a formal validation step that requires executing proving commands and interpreting their outputs to guard against premature success claims before merging.

Prevent premature success claims in local development by enforcing a verification step that requires fresh test, lint, and build evidence before marking work as done or ready for review.

Yes, agent-assisted task completion requires explicit verification evidence by identifying the proving command, executing it, reading the full output, and verifying results before declaring completion.

Automated completion verification is limited by its dependence on predefined proving commands; it only validates the specific tests, linters, and builds explicitly configured in your software project workflow pipelines.