verification-before-completion

Code verification before completion requires running appropriate test and build commands, reviewing their outputs, and confirming the evidence supports your success statement before reporting the task as finished.

Evidence-based reporting for software completion means using fresh test results, build outputs, and requirement checks as the required basis for stating that a bug fix, commit, or pull request is successful.

Preventing unsupported claims when fixing bugs requires enforcing a verification gate where you run validation checks, inspect the actual outputs, and only report success after reviewing the proof.

You need to run tests before creating a pull request to validate requirement implementation, inspect the test outputs, and use those verified results as evidence to confirm the actual project status.

The best way to validate requirement implementation before committing code is to execute the relevant verification commands, review the build and test outputs, and assert completion only if the evidence proves it.