verification-loop

Run build, type-check, lint, test, and security scans before PR submission.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Mang30/myskills --skill verification-loop-mang30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Mang30/myskills/tree/main/skills/verification-loop
Command: npx skills add https://github.com/Mang30/myskills --skill verification-loop-mang30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents weak or broken changes from reaching a PR by running a comprehensive, repeatable verification loop that checks build success, type correctness, code quality, test correctness, security risks, and change scope before you proceed.

Core Features & Use Cases

  • End-to-end validation pipeline: Build, type-check, lint, run tests with coverage, perform lightweight security scanning, and review diffs.
  • Quality gate before PR: Use it when you complete features or make major code changes so the submission is based on a verified state.
  • Refactoring and ongoing sessions: Re-run regularly during long work to detect regressions promptly and maintain confidence while iterating.

Quick Start

Run the full verification loop before opening or updating a PR to ensure the branch is ready.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run a comprehensive code verification loop before a pull request?

Run a comprehensive code verification loop to validate build success, type checking, linting, test coverage, and security scanning before submitting a pull request. This prevents weak or broken changes from reaching the PR.

Can I use this verification workflow for both JavaScript and Python repositories?

Yes, this verification workflow applies to both JavaScript/TypeScript and Python repositories, running a repeatable validation pipeline across build, type correctness, testing, and security scanning.

What is the best way to catch build, type, and lint issues early in development?

The best way to catch build, type, and lint issues early is to run an end-to-end validation pipeline during feature completion or major code changes, enforcing failure-stop behavior across stages to maintain confidence.

Does the automated verification process include security and secret scanning?

Yes, the automated verification process includes lightweight security and basic secret scanning alongside diff-based review, checking for security risks and change scope before you proceed to a PR.

When should I run a quality gate validation pipeline on my codebase?

Run the quality gate validation pipeline when completing features, making major code changes, or during long refactoring sessions to detect regressions promptly and ensure the branch is ready for PR submission.