verification-loop

Run build, type, lint, test, and security checks before PR submission.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of broken builds, failing tests, and missing security checks by enforcing a repeatable verification sequence before code is merged.

Core Features & Use Cases

  • Build verification: Confirms the project compiles successfully using the repo’s build command.
  • Quality checks: Runs type checking and linting to catch correctness and style issues early.
  • Confidence checks: Executes the test suite with coverage expectations and performs lightweight security scanning (secrets and debug output).
  • Change awareness: Reviews the diff summary to ensure modifications are intentional and reviewable.
  • Use case: You refactor a critical module and want to ensure the build still passes, TypeScript types stay consistent, linting remains clean, tests still pass with acceptable coverage, and no accidental secrets or console logging were introduced.

Quick Start

Run verification before opening your pull request after completing a significant change in your repository.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run code verification checks before submitting a pull request?

To run code verification before a PR, execute a structured sequence of build, type, lint, test, and security checks. This generates a VERIFICATION REPORT with PASS/FAIL outcomes, finding counts, coverage percentage, and an overall readiness decision.

What is included in a pre-PR quality gate check for TypeScript and Python?

A pre-PR quality gate check includes build verification, type checking, linting, test suite execution with coverage expectations, lightweight security scanning for secrets, and diff review to ensure changes are intentional and reviewable.

How do I prevent broken builds and failing tests after refactoring a module?

To prevent broken builds and failing tests after refactoring, run a repeatable verification sequence that confirms compilation, type consistency, linting cleanliness, test coverage, and checks for accidental secrets or console logging before merging.

Does this verification process work with both JavaScript and Python projects?

Yes, this verification process works with JavaScript/TypeScript and Python projects. It requires applying quality gates and regression prevention after refactors, feature work, or major modifications to ensure code readiness.

What does a structured verification report contain for code review readiness?

A structured verification report contains PASS/FAIL outcomes, counts for type, lint, test, and security findings, coverage percentage, diff file count, and an overall readiness decision to determine if changes are ready for PR submission.

When should I run build and security scanning checks in my development workflow?

You should run build and security scanning checks before opening your pull request after completing a significant change in your repository, ensuring that code changes pass all verification steps before merging.