verification-before-completion

To verify work completion before claiming a pull request is done, run specific verification commands and review their output to confirm successful task execution. This process gatekeeping ensures evidence-based claims and accuracy in software development.

The best way to enforce process integrity before a pre-commit task is to establish a checkpoint that mandates running verification commands. Reviewing command output confirms work validation and prevents unverified completion claims in the software development lifecycle.

Claiming work completion without verification causes issues because it bypasses process integrity and risks delivering unvalidated outputs. Executing verification commands provides the evidence needed to support completion claims, promoting honesty and quality in software development.

Yes, you can use this approach to validate work outputs for both pre-commit and pre-PR tasks. It focuses on the software development lifecycle by requiring command execution and output review to ensure no completion claim is made without proper work validation.

To implement evidence-based completion claims in your software development workflow, run the verification command for your specific task and confirm the output indicates successful completion. This ensures process gatekeeping before any work validation claim is made.

Relying on manual completion checks instead of execution-based verification limits process integrity because it lacks command output evidence. Without executing verification commands, completion claims remain unverified, reducing accuracy and quality in the software development lifecycle.