verification-looplisted

Build, type-check, lint, test, secret-grep, and diff-review quality gate for code changes. Use when you have finished a feature or significant change, are about to open a PR, or want to confirm quality gates pass after refactoring — running the full verify sequence and reporting pass/fail per phase. Detects the project's own toolchain rather than assuming one. For the one-shot slash command, see /verify.
sardonyx0827/dotfiles · ★ 0 · Code & Development · score 75

Install: claude install-skill sardonyx0827/dotfiles

# Verification Loop Skill A comprehensive verification system for Claude Code sessions. ## When to Use Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring ## Verification Phases ### Phase 0: Detect the Toolchain Run the project's own commands, not a hardcoded stack. Detect before running: | Marker | Build | Types | Lint | Test | Coverage | | ----------------------------- | ---------------- | ------------------ | --------------- | --------------- | ------------------------------- | | `package.json` | `<pm> run build` | `npx tsc --noEmit` | `<pm> run lint` | `<pm> test` | `<pm> test -- --coverage` | | `go.mod` | `go build ./...` | (compiler) | `go vet ./...` | `go test ./...` | `go test -cover ./...` | | `pyproject.toml` / `setup.py` | (n/a) | `pyright .` | `ruff check .` | `pytest` | `pytest --cov` | | `Cargo.toml` | `cargo build` | (compiler) | `cargo clippy` | `cargo test` | `cargo llvm-cov` (if installed) | `<pm>` is the package manager implied by the lockfile (`pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `package-lock.json` → npm). A `scripts` entry in `package.json` always wins over the table — read it first. If the repo define