Verification Before Completion

This enforces a hard rule against claiming code works without running verification commands first. It catches you before saying "tests should pass" or "build looks good" and forces you to actually run the test suite, linter, or build command and show the output. Prevents the classic workflow killer where you commit broken code because you assumed your changes worked. The skill is pretty militant about it, blocking any success claims until you've executed the verification step and can point to actual command output showing zero failures. Useful when you're tired and tempted to skip the verification step.