verification-loop

Name: verification-loop
Availability: InStock
Author: kk20300113-png

Run six-phase pre-pull request verification for JavaScript, TypeScript, and Python projects.

Updated May 9, 2026

Search Tags:#quality gates #test coverage #security scanning #code verification #build validation #diff review #pre-pr checks

Ready to run

npx skills add https://github.com/kk20300113-png/my-claude-skills --skill verification-loop-kk20300113-png

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/verification-loop
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill verification-loop-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually running build, lint, test, and security checks before opening a pull request is time-consuming and easy to forget, leading to broken builds, unreviewed bugs, and security vulnerabilities being merged into the codebase.

Core Features & Use Cases

6-Phase Verification Workflow: Automates build validation, type checking, linting, test coverage checks, secret scanning, and diff review in a standardized sequence.
Clear Pass/Fail Reporting: Generates a structured verification report with explicit status for each check and an overall readiness verdict for PR creation.
Use Case: After completing a new payment processing feature, run this skill to confirm the build passes, tests meet the 80% coverage threshold, no API keys are accidentally committed, and only intended changes are included before submitting your PR.

Quick Start

Use the verification-loop skill to run a full quality check on your latest code changes before creating 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 automate pre-PR code quality checks for JavaScript and Python projects?▼

Automate pre-PR code quality checks by running a 6-phase verification workflow that sequentially validates builds, detects type errors, enforces linting, checks test coverage, scans for secrets, and reviews diffs for JavaScript, TypeScript, and Python projects.

What is included in a pre-merge build validation workflow?▼

A pre-merge build validation workflow includes build success checks, type error detection, linting validation, test coverage threshold enforcement, secret exposure scanning, and intentional change review to generate a structured readiness verdict.

How do I enforce test coverage thresholds and prevent secret exposure before creating a pull request?▼

Enforce test coverage thresholds and prevent secret exposure by running automated pre-PR checks that verify an 80% coverage metric and scan committed code for accidentally included API keys before generating a pull request.

Can I use this verification loop for TypeScript post-development workflows?▼

Yes, you can use this verification loop for TypeScript post-development workflows, as it explicitly supports JavaScript, TypeScript, and Python projects by applying standardized quality gates before merging code into shared repositories.

What is the best way to standardize manual pre-pull request quality gates?▼

The best way to standardize manual pre-pull request quality gates is replacing them with an automated sequence that produces clear pass/fail reporting, ensuring no broken builds, unreviewed bugs, or unintended code changes reach shared repositories.

Why do I need diff review in my pre-merge code verification process?▼

You need diff review in your pre-merge code verification process to catch unintended code changes, ensuring that only intentional modifications pass quality gates and preventing unreviewed bugs from being merged into shared repositories.