verification-before-completion

Run the exact verification command fresh, read its full output and exit code, and only then assert success with concrete evidence. This prevents false completion claims before creating a pull request by requiring actual proof.

Your CI agent likely lacks a verification gate. Require it to execute the full test command, inspect the output and exit code, and include concrete evidence before stating any positive status or claiming code quality checks pass.

Pre-commit verification evidence is the fresh output and exit code from running your exact proof command, such as tests or linters. It works by acting as a gate that blocks any success claim until you inspect the complete output.

Enforce red-green regression testing verification by requiring automated agents to run the exact test command, inspect the full output and exit code, and report the actual status with evidence rather than asserting completion blindly.

The best way to verify a bug fix before marking a sprint task as done is to run the exact verification command fresh, read its full output and exit code, and only state success if the evidence proves it passed.

If your pre-commit verification command fails, report the actual status with the output evidence and outline the next steps to fix it, rather than asserting completion or claiming the work is done.