verification-before-completion

To verify commit readiness, you must execute specific verification commands, confirm that all tests pass and linters are clean, and validate that outputs meet requirements before reporting task completion or merging a code PR.

Evidence-based verification in task management is the process of requiring specific command outputs as proof of code quality, ensuring that claims of work completion are backed by actual test results and clean linter checks.

Yes, you can use this process in code review and task management. It integrates by prompting users to verify tests pass, linters are clean, and all requirements are met before finalizing task status or merging pull requests.

No external dependencies are needed to ensure workflow integrity before a PR. The process works by prompting users to run existing verification commands and review their outputs directly within their current environment.

Reporting task status without verification causes workflow issues because unverified claims introduce hidden errors and misunderstandings, compromising code quality and breaking workflow integrity before the code reaches the commit stage.