verification-before-completion

This Skill enforces a mandatory verification process by requiring developers to execute verification commands and review outputs thoroughly before claiming task completion, preventing false success assertions.

Claiming task completion without verification causes errors and defective deliveries because it bypasses the mandatory process of executing verification commands and reviewing their outputs to confirm code correctness.

The best way to ensure quality assurance before a release is to enforce a structured framework that validates code tests, build statuses, and requirements before progressing, preventing false success claims.

Yes, you need to run designated verification commands for quality assurance to reliably confirm task completion, validate code correctness, and maintain quality standards during development and releases.

Mandatory verification prevents false claims of success by enforcing the execution of verification commands and thorough output reviews, ensuring developers reliably confirm task completion and maintain quality standards.

You need to validate build statuses during the development process when preparing to push code or approve a change, ensuring all tests and builds pass before progressing to prevent defective deliveries.