verification-before-completion

To prevent premature code completion claims, enforce a strict verification protocol that requires running tests, linters, and build commands to review output evidence before asserting success, passing, or task completion.

The best way to verify code quality before creating a Pull Request is to run mandatory verification commands, such as tests and linters, and explicitly review their output to ensure no incomplete work or unfixed bugs are shipped.

Enforcing a verification process reduces errors by preventing the release of faulty work, ensuring that claims of passing tests or fixed bugs are backed by explicit execution and review of verification command outputs.

Yes, you can use this verification enforcement for task management and status reporting, as it applies to all development stages by requiring explicit evidence from verification commands before any task success is claimed.

No dependencies are required to enforce this verification protocol, as it functions by mandating the execution and review of existing tests, linters, and build processes before any claims of completion or passing are made.