verification-before-completion

To enforce verification evidence before a pull request is marked complete, identify the exact verification command, execute it fully, parse the outputs, and validate the results before allowing any completion statements. This prevents premature status changes by requiring fresh test, build, and lint outputs.

Evidence-based completion in software development workflows is the practice of requiring fresh verification evidence before any status change, PR, or release decision. It ensures claims are justified by executing tests, builds, and lint checks, parsing the outputs, and validating the results prior to task closure.

To prevent premature task closure during code reviews and CI gates, require fresh verification outputs from tests, builds, and lint checks before allowing completion claims. This validates that all functional requirements are met and blocks unverified status changes or deployment decisions.

To validate lint and test results before claiming a coding task is finished, identify the required verification command, execute it fully, and parse the outputs. By verifying these results, you ensure that all functional requirements are satisfied before making any completion statements.

Yes, this verification process works without external dependencies. It functions independently to identify verification commands, execute them, parse outputs, and validate results, ensuring that completion statements are backed by fresh evidence within your software development workflow.

You should require fresh verification outputs in your development workflow before any claim of completion, status change, PR merge, or release decision. This prevents unverified claims by ensuring tests, builds, and lint results are validated immediately prior to task closure.