What problem does it solve? Work is often marked complete without adequate validation, leading to undetected regressions and broken builds. This Skill enforces a disciplined verification loop so every change is checked against the smallest meaningful set of tests and checks before being declared done. ## Core Features & Use Cases - Risk-Based Validation Ordering: Runs fast targeted checks first, then escalates to broader lint, type, build, and packaging checks as risk grows. - Explicit Verification Reporting: Compares expected versus actual results and reports exactly what was verified and what was not. - Honesty Guardrails: Prevents claiming verification that was never run and forces explicit statements of blockers and skipped checks. - Use Case: After refactoring a payment module, run the verification loop to execute the module's unit tests, then lint and type checks, and finally a manual review of the high-risk transaction paths before merging. ## Quick Start Before marking this task complete, run the verification loop to validate my changes with the appropriate tests and checks.