skill-verify

To enforce verification of test results before declaring a build complete, execute testing commands, read outputs, and confirm zero failures before finalizing status updates. This guided process ensures claims are backed by actual evidence.

The best way to prevent false completion claims during software quality checks is to implement a verification enforcement procedure that requires reading test outputs and confirming zero failures before marking any task as done.

To verify automated tests pass before releasing code, follow a step-by-step process to identify, run, and read testing commands, ensuring all checks pass with zero failures before finalizing the release status.

Yes, QA teams ensuring code integrity can use this verification process to enforce rigorous procedures for software testing and builds, preventing unverified claims of completion by requiring actual execution and review of outputs.

Claiming task completion without evidence causes software errors because it allows false success claims to bypass quality checks. Enforcing verification with actual test outputs reduces dishonesty and prevents unverified code from passing builds.