verification-before-completion

Verify code changes before committing by running a structured verification process that checks commands, output, and results. This pre-commit verification identifies mistakes early and requires evidence-based proof of successful execution before advancing.

Pre-commit verification is a rigorous process of checking task completion criteria before creating pull requests. It is needed for development best practices because it ensures accuracy and honesty in project reporting by requiring evidence-based claims over anecdotal satisfaction.

Yes, a verification checklist works for both software development and general task completion. It validates that any task requiring proof of successful execution meets necessary criteria before you move on or delegate the work.

The best way to enforce commit hygiene is to require a comprehensive verification process that checks commands and validates output before claiming work completion. This approach catches mistakes before changes are committed.

Yes, you can use scripts to automate the validation of task completion criteria before a pull request. Running a verify-work command executes structured checks to confirm all development tasks meet the required proof of execution.

You should not skip pre-commit verification when working on tasks requiring proof of successful execution, but it may be unnecessary for trivial changes. However, for maintaining strict commit hygiene and accurate project reporting, verification is always recommended.