verification-before-completion

To enforce verification before claiming a build is complete, run your verification commands and review their outputs before updating any task status. This prevents premature assertions by mandating fresh evidence.

Gate-style verification for pull requests mandates running tests, lint checks, and builds, then assessing their outputs. It ensures work is only declared complete after producing fresh, traceable evidence.

Prevent premature success claims by running verification commands and confirming their outputs before declaring success. This approach preserves honesty and traceability across tests, linting, and pull requests.

Yes, you can use this verification approach universally across development tasks such as tests, linting, builds, and pull requests to preserve honesty and ensure audit-ready evidence for accountability.

Produce audit-ready evidence by running verification commands and capturing their outputs before declaring work complete. This generates a reproducible trail of verification steps and outcomes for accountability.

The best way to ensure traceability before declaring work done is to run verification commands, assess their outputs, and only then claim success. This prevents premature assertions and produces fresh evidence.