verification-loop

Automate build, type, lint, test, security, and diff checks for JavaScript, TypeScript, and Python.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill verification-loop-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/verification-loop
Command: npx skills add https://github.com/luongldptit/move-ticket --skill verification-loop-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of merging broken, buggy, or insecure code by automating end-to-end quality verification checks before pull requests are created, reducing reviewer overhead and preventing production issues.

Core Features & Use Cases

  • Multi-phase verification pipeline: Runs build, type checking, linting, test suite with coverage, security scanning, and diff review in a standardized sequence.
  • Automatic quality gate enforcement: Halts the verification process immediately if critical failures (such as broken builds) are detected, preventing low-quality code from progressing.
  • Use case: Run this skill after completing any feature, refactor, or significant code change to catch issues early, before submitting a pull request for review.

Quick Start

Invoke the verification-loop skill after finishing a code change to run all quality checks and receive a clear readiness report for your 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 automate pre-pull request code quality verification for JavaScript and Python?

Pre-pull request code quality verification is automated by running a multi-phase pipeline that executes build validation, type checking, linting, test coverage, and security scanning to generate a structured readiness report for JavaScript, TypeScript, and Python projects.

What is included in a pre-PR build validation and security scanning sequence?

A pre-PR build validation and security scanning sequence includes build checks, type checking, lint execution, test suite coverage enforcement, secret scanning, and change diff review, halting immediately upon detecting critical failures to prevent broken code progression.

Can I run test coverage enforcement and lint checks for TypeScript projects after refactoring?

Yes, you can run test coverage enforcement and lint checks for TypeScript projects after refactoring. The verification process applies to post-refactor validation and post-feature completion quality gates to catch issues before pull request submission.

Does automated secret scanning and code verification stop when a broken build is detected?

Automated secret scanning and code verification does stop when a broken build is detected. Automatic quality gate enforcement halts the verification process immediately upon critical failures, preventing low-quality or insecure code from progressing further.

What is the best way to prevent insecure code from being merged into my codebase?

Preventing insecure code from being merged is best achieved by automating end-to-end quality verification checks before pull requests are created, applying secret scanning and diff review to reduce reviewer overhead and eliminate production issues.