Runs a six-stage verification loop for code changes: build, type check, lint, tests, security scan and diff review.
- What it does
- This skill defines a staged verification workflow for a coding session. It runs build, type checking, linting, test suites with coverage, secret and console.log scanning, and a git diff review, then produces a pass/fail verification report with an overall READY or NOT READY verdict for a pull request. It also describes a continuous mode with mental checkpoints and notes how it complements PostToolUse hooks.
- When to use it
- Use it after finishing a feature or major code change, before creating a pull request, after refactoring, or whenever quality gates need to be confirmed. It is also intended for long sessions where verification should run every 15 minutes or after significant changes.
- Requirements
- Requires a project with build, lint and test commands (examples use npm/pnpm, tsc, pyright, ruff) plus git for diff review. It contains instructions only, with no bundled scripts, and assumes shell access to run the listed commands.