verification-loop

Runs build, type-check, lint, test, security, and diff review phases to verify code changes before PRs.

5|Updated Jul 8, 2019
One-click install
npx skills add https://github.com/rinchsan/dotfiles --skill verification-loop-rinchsan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/rinchsan/dotfiles/tree/main/.claude/skills/verification-loop
Command: npx skills add https://github.com/rinchsan/dotfiles --skill verification-loop-rinchsan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected build failures, type errors, lint violations, or failing tests. This Skill provides a structured multi-phase verification workflow that catches quality issues before a pull request is created. ## Core Features & Use Cases - Six-Phase Verification: Sequentially runs build verification, type checking, lint and format checks, test suites with coverage, security scans, and git diff review. - Multi-Language Support: Covers Node.js/TypeScript (npm, pnpm, tsc, Prettier), Python (pyright, ruff), and Go (go build, go vet, golangci-lint, go test) toolchains. - Structured Reporting: Produces a standardized verification report with PASS/FAIL status per phase and an overall READY/NOT READY verdict for PRs. - Use Case: After refactoring a TypeScript module, invoke the skill to confirm the build passes, Prettier formatting is clean, tests meet the 80% coverage target, and no debug statements remain before opening a PR. ## Quick Start Run the verification loop on my current changes and tell me whether the code is ready for a pull request.

Frequently Asked Questions about verification-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code quality before creating a pull request?

Run a multi-phase verification covering build, type checking, linting, tests with coverage, security scanning, and diff review. This skill executes each phase with the appropriate toolchain commands and reports an overall READY or NOT READY verdict.

How to run type checking and linting for TypeScript projects?

Use npx tsc --noEmit for type checking and npm run lint plus npx prettier --check for lint and format validation. If Prettier fails, auto-fix with prettier --write and re-run the check to confirm.

Does this verification workflow support Go and Python projects?

Yes, it includes Go phases using go build, go vet, golangci-lint, and go test -cover, plus Python phases using pyright for type checking and ruff for linting. Each language has dedicated commands per verification phase.

What test coverage threshold does the verification require?

The test phase targets a minimum of 80% coverage, measured via npm run test -- --coverage for Node.js or go test -cover for Go. The report lists total, passed, and failed tests alongside the coverage percentage.

When should I run verification during a long coding session?

Run it after completing each feature or significant change, before creating a PR, and after refactoring. In continuous mode, trigger verification roughly every 15 minutes or at checkpoints like finishing a function or component.