verification-before-completion

To prevent false completion claims before a pull request, enforce an evidence-before-claims gate that requires running full verification commands and checking fresh output before asserting any work is done.

Evidence-based reporting for software builds and tests is the practice of executing exact verification commands, reading complete outputs, and confirming exit statuses before making any success or completion statements.

Verify test and linting results before committing code changes by running the complete relevant checks fresh, confirming the exit status from the full output, and only then reporting completion status.

Yes, anti-pattern protection blocks satisfaction language and paraphrases of done when fresh verification evidence, such as full command outputs and exit statuses, was not produced in the same message.

You need to enforce regression verification in CI/CD workflows before pre-commit or pre-PR status reporting to ensure code changes, bug fixes, and build checks are fully validated with fresh evidence.