verification-loop

Runs verification loop checks on code changes for a readiness report.

Updated May 14, 2026
One-click install
npx skills add https://github.com/WUIX69/e-lock --skill verification-loop-wuix69
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/WUIX69/e-lock/tree/main/.agent/.agents/skills/verification-loop
Command: npx skills add https://github.com/WUIX69/e-lock --skill verification-loop-wuix69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It catches broken builds, type regressions, lint issues, failing tests, and risky changes before code is merged or released.

Core Features & Use Cases

  • Build and Type Validation: Confirms the project still compiles and the type system still passes after edits.
  • Quality Gate Checks: Runs linting, test coverage review, and security scans to catch common regressions early.
  • Change Review Workflow: Inspects the diff for unintended edits, missing error handling, and edge cases before a PR.
  • Use Case: After a refactor or feature finish, use this skill to produce a structured readiness report for the team.

Quick Start

Ask the skill to run the full verification loop on the current changes and summarize any failures in a readiness report.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run pre-PR verification checks for build, lint, and tests?▼

Pre-PR verification requires sequential execution of build validation, type checking, linting, test coverage review, secret scanning, and changed-file inspection to catch regressions before code is merged.

What is the best way to catch code regressions before merging a refactor?▼

To catch regressions before merging a refactor, run a full verification loop covering build and type validation, quality gate checks, and a diff review workflow to produce a structured readiness report.

How does a post-change validation workflow handle security and diff inspection?▼

Post-change validation handles security by running secret scans and manages diff inspection by reviewing changed files for unintended edits, missing error handling, and edge cases before generating a readiness report.

Does the verification loop check test coverage and type regressions for application code?▼

Yes, the verification loop checks test coverage and type regressions by sequentially running type checking and test coverage review alongside build validation, linting, and security scans for application code.

When do I need to run a full verification loop on my code changes?▼

You need to run a full verification loop after finishing a feature, completing a refactor, preparing a release, or conducting a pre-PR review to ensure build, type, lint, test, and security checks pass.

What does a readiness report include after running build and type validation checks?▼

A readiness report summarizes any failures found during sequential build verification, type checking, linting, test coverage review, secret scanning, and changed-file inspection, providing a structured overview for the team.