What problem does it solve? Code changes often reach pull requests without systematic quality checks, letting build failures, type errors, failing tests, or leaked secrets slip through. This Skill enforces a structured multi-phase verification loop so every change is validated before review. ## Core Features & Use Cases - Six-Phase Verification: Sequentially runs build validation, type checking (tsc/pyright), linting (npm lint/ruff), test suites with coverage thresholds, security scans for hardcoded secrets, and git diff review. - Standardized Report: Produces a pass/fail verification report summarizing each phase with an overall READY/NOT READY verdict and a list of issues to fix. - Continuous Mode: Supports periodic re-verification every 15 minutes or after major changes during long coding sessions. - Use Case: After refactoring a TypeScript module, invoke the verification loop to confirm the build passes, tests maintain 80% coverage, no API keys leaked into source files, and the diff contains only intended changes before opening a PR. ## Quick Start Run the verification loop on my current changes and generate a readiness report before I create a pull request.