Verification Before Completion

Match each completion claim to fresh evidence from the current revision. This skill checks the claim; it does not replace a task contract, QA plan, or the project's test procedure.

Check the claim

1. Write down the exact behavior or state you intend to report.
2. Select the smallest relevant verification channel: automated test, build, manual reproduction, artifact inspection, or explicit user acceptance.
3. Run or inspect that channel after the last relevant edit. Record the command or manual steps, target revision, result, and any skipped scope.
4. Compare the result with the claim. A passing linter does not prove a build; a passing build does not prove behavior; a changed file does not prove a bug is fixed.
5. Report only what the evidence supports. If verification is unavailable, identify the unverified claim and the specific blocker.