What problem does it solve? Code changes often ship with undetected build failures, type errors, lint violations, failing tests, or leaked secrets. This Skill enforces a structured quality gate so every change is verified across six phases before a PR is created. ## Core Features & Use Cases - Six-Phase Verification: Sequentially runs build, type check, lint, test suite with coverage, security scan for secrets and debug statements, and git diff review. - Stack-Adaptive Commands: Detects Python (uv, pytest, ruff, pyright) versus Node.js/TypeScript (npm, pnpm, tsc) projects and selects the appropriate commands via a stack-detection reference. - Standardized Report: Produces a PASS/FAIL verification report with an overall READY/NOT READY verdict and a list of issues to fix. - Use Case: After refactoring a Python service, ask for verification to confirm the build passes, pytest coverage holds, no API keys leaked into the diff, and the change is ready for PR. ## Quick Start Ask the assistant to run the verification loop on the current changes and report whether the branch is ready for a PR.