verification-before-completion

To enforce running tests before claiming code review completion, this Skill mandates executing verification commands fresh and checking their output before any success assertion is made. It prevents false positives by requiring current evidence for all completion claims.

The best way to prevent false positive assertions during quality assurance is to require evidence-based verification before any declarative statement about work status. This protocol ensures commands proving a claim are run fresh and their output is checked before reporting success.

You verify task completion using assertions by running the specific test suite or build command, confirming zero failures in the output, and then stating the task is complete with that evidence. This prevents assuming code works without actual current proof.

Yes, you can use this verification protocol for bug fixing as well as building. It applies to all stages of development where work status is reported, requiring specific verification commands to be run and analyzed before making any declarative statements about the work's state.

Claiming tests pass without running them causes costly rework because premature claims of completion bypass actual evidence-based verification. Without running commands fresh and checking their output, false positives propagate, leading to discovered failures later in the development cycle.

No, you do not need any specific testing frameworks installed to use this verification protocol. It operates without dependencies, applying a strict protocol to whatever testing, building, or linting commands your environment already uses to verify task completion.