verification-loop

Automate end-to-end verification of Claude Code sessions across TypeScript, Python, and JavaScript projects.

Updated May 27, 2025
One-click install
npx skills add https://github.com/vinwang/tools --skill verification-loop-vinwang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/vinwang/tools/tree/main/iflow/skills/verification-loop
Command: npx skills add https://github.com/vinwang/tools --skill verification-loop-vinwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and enforces a multi-phase verification process to catch regressions in Claude Code sessions before changes are merged.

Core Features & Use Cases

  • Phase-driven checks across Build, Type Check, Lint, Tests, Security, and Diff Review to validate code quality.
  • Guidance on when to use: after feature completion, before PR creation, and after refactoring to catch unseen issues.
  • Output: produces a structured verification report with pass/fail status and coverage metrics to inform PR decisions.

Quick Start

Run the verification loop after completing a feature or refactor to ensure all quality gates pass.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I automate end-to-end verification for TypeScript and Python code before a pull request?

Automated end-to-end verification runs multi-phase checks across build, type check, lint, tests, and security scans to catch regressions before PRs. It produces a structured verification report with pass/fail status and coverage metrics to inform merge decisions.

What is the best way to run quality gates on code changes after refactoring?

Running quality gates after refactoring involves applying a phase-driven workflow that validates build, type check, lint, tests, security, and diff review. This ensures unseen issues are caught before PR creation by enforcing checks across TypeScript, Python, and JavaScript projects.

Does the automated verification loop work with JavaScript projects?

Yes, the automated verification loop works with TypeScript, Python, and JavaScript projects. It guides builds, type checks, lint, tests, and security checks across these languages to validate code quality and output a structured verification report.

When do I need to run a security scan and diff review during code verification?

A security scan and diff review are needed after feature completion or refactoring to catch unseen issues before PR creation. These phases are part of an end-to-end verification process that produces a structured report with pass/fail status to inform PR decisions.

How do I generate a structured verification report with pass/fail status and coverage metrics?

To generate a structured verification report, run an end-to-end verification loop that executes build, type check, lint, test, and security scan phases. The output report contains pass/fail status and coverage metrics to guide PR decisions.