verification-loop

Runs build, type, lint, test, security, and diff checks before pull requests.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill verification-loop-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/everything-claude-code/docs/zh-TW/skills/verification-loop
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill verification-loop-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 verification loop that checks build success, type errors, lint warnings, test results with coverage, security issues, and the git diff. The process outputs a readiness report indicating whether the changes are ready for PR.

What checks should run before merging code changes?

Essential pre-merge checks include build validation, static type checking with tsc or pyright, linting with npm lint or ruff, test suites with coverage thresholds, secret scanning, and manual diff review for unintended changes.

How do I scan code for leaked API keys and secrets?

Use grep to search source files for patterns like sk- prefixes and api_key strings across TypeScript and JavaScript files. The verification loop also flags leftover console.log statements that may expose sensitive runtime data.

Does this verification work for both TypeScript and Python projects?

Yes, the verification phases include commands for both ecosystems. TypeScript projects use tsc --noEmit and npm scripts, while Python projects use pyright for type checking and ruff for linting.

What test coverage threshold should I enforce before a PR?

The verification loop targets a minimum of 80% code coverage. Tests run with the coverage flag, and the report shows total tests, passed, failed, and the coverage percentage for evaluation.

How often should verification run during long coding sessions?

In continuous mode, run verification every 15 minutes or after major changes such as completing a function or component. This catches regressions early instead of accumulating issues until the end of the session.