verification-before-completion

To prevent false completion claims before creating a pull request, enforce fresh verification by running the relevant build or test command and inspecting the output. Evidence-based reporting ensures you only claim success after confirming actual results.

Evidence-driven reporting for build validation and bug fixes requires running the relevant command, inspecting the output, and reporting only verified results before making any success claim. This mechanism prevents premature statements of correctness.

To verify test readiness before claiming a task is complete, execute the exact test command and read the output to confirm it passes. This completion gatekeeping step ensures your status assertions are backed by fresh evidence.

Yes, you need to run build commands before stating a bug fix is ready to ship. Fresh verification enforces command execution and output inspection, ensuring your success claims are always backed by actual evidence.

Claiming a regression check passes without command execution causes issues because it skips output inspection and evidence-based reporting. Without fresh verification, you risk making premature completion claims that hide unresolved build or test failures.

The best way to enforce verification before completion claims is to gatekeep the process by requiring command execution, output inspection, and evidence-based reporting. This prevents premature success assertions for testing, builds, and pull requests.