verification-before-completion

To verify code changes before committing, run predefined verification commands and review their output. This pre-commit verification process ensures your work claims are backed by evidence, preventing inaccurate task completion or bug fix reports.

Evidence-based work claim verification requires running specific commands to prove a task is complete or a bug is fixed. It prevents premature celebrations by ensuring developers provide concrete output evidence before reporting changes.

Stop premature bug fix claims by integrating customizable verification commands into your workflow. Running these commands before reporting completion ensures all assertions are backed by actual output, maintaining high software quality standards.

Yes, you can customize verification commands for different scenarios. This flexibility allows you to specify exact checks required for various tasks, ensuring accurate commit verification tailored to your specific software quality needs.

You need to run commit verification immediately before reporting changes or committing to a repository. This pre-commit step checks the output of your verification commands to ensure claims of task completion are accurate and evidence-based.

The limitation of predefined verification commands is that they require you to manually specify the correct checks for each scenario. Verification only proves the specified commands pass, meaning untested edge cases might still cause issues after committing.