ywc-verify-done

To enforce verification before a commit, implement a mandatory gate requiring fresh shell command execution and output analysis. This structured protocol ensures evidence-backed assertions by running tests and builds, reducing CI failures from unverified changes.

The best way to verify task completion for a pull request is applying a five-step protocol: identify, run, read, verify, and claim. This process forces you to analyze actual shell command output, ensuring tests and linting pass before declaring work finished.

Evidence-based verification is needed to counter rationalization and false-positive completion claims. By requiring fresh shell command output analysis, it prevents unverified assertions and ensures that tests, builds, and linting actually pass in the current environment.

The five-step verification protocol works by sequentially identifying the task, running shell commands, reading the output, verifying the results, and then making a completion claim. This strict adherence prevents skipping steps and ensures every assertion is backed by fresh evidence.

No, you should not skip verification for trivial changes. The verification gate includes a rationalization defense framework specifically designed to counter excuses like cached confidence or triviality, ensuring strict adherence to evidence-backed checks across all software development workflows.

Yes, automated verification reduces CI failures during task handoff by enforcing a mandatory gate that requires fresh shell command execution. By surfacing test, build, and linting output before completion claims, it guarantees all assertions are evidence-backed in the current environment.