verification-before-completion

To verify builds and tests before a pull request, you must identify the exact proving command, execute the full verification in the current session, check the exit code and output, and report the actual status with evidence.

Claiming a pull request is passing without fresh verification causes issues because it relies on partial checks or confidence language instead of executed evidence, leading to dishonest or premature completion claims.

The best way to enforce evidence before asserting code completion is to require fresh verification output, such as testing, linting, and build confirmation, validating the exit code prior to commits or PR creation.

To stop premature completion claims during regression confirmation, identify the exact proving command, run the full check in the current message, read the full output, and confirm the verified state.

You cannot use confidence language instead of executed evidence for readiness checks because this approach flags typical mistakes by requiring fresh command output to validate the actual status before pushing.

You need to run fresh verification commands before a commit when you are about to express satisfaction or claim completion, ensuring you verify tests, builds, and key requirements with fresh output.