verification-loop

Run build, type checking, linting, tests, security scans, and diff review on repository changes.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/samymity/bridge-ventures-backend --skill verification-loop-samymity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/samymity/bridge-ventures-backend/tree/main/.claude/skills/verification-loop
Command: npx skills add https://github.com/samymity/bridge-ventures-backend --skill verification-loop-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or risky changes from reaching a PR by enforcing a repeatable verification loop across build, types, lint, tests, security checks, and diff review.

Core Features & Use Cases

  • Build Verification: Ensures the project compiles and bundles successfully before continuing.
  • Type & Lint Gates: Detects TypeScript and style/quality issues early to reduce review churn.
  • Test, Coverage, and Security Scans: Runs the test suite with coverage expectations and flags common issues like secrets and debug logging.
  • Diff Review: Helps reviewers focus on what changed and identify unintended behavior, missing error handling, and edge-case risks.

Quick Start

Run the verification loop at /verify after completing a feature and before opening the pull request to confirm the change 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 pre-PR quality gates for JavaScript and Python codebases?▼

Pre-PR quality gates are enforced by running build, type checking, linting, tests with coverage, security scanning, and diff review, producing a structured pass/fail verification report that stops on failures.

What is the best way to verify pull request readiness and catch build or security issues fast?▼

Pull request readiness is verified by executing a repeatable verification loop across build, types, lint, tests, security checks, and diff review to prevent broken or risky changes from reaching a PR.

Can I use a verification loop to check test coverage and security scanning before opening a pull request?▼

Yes, the verification loop runs the test suite with coverage expectations and flags common security issues like secrets and debug logging before opening a pull request.

How does git diff review identify unintended behavior and edge-case risks during code verification?▼

Git diff review helps reviewers focus on what changed to identify unintended behavior, missing error handling, and edge-case risks during code verification.

Does the verification loop stop on linting or type checking failures to ensure changes are PR-ready?▼

Yes, the verification loop stops on failures so the overall result is PR-ready only when all gates including type checking and linting succeed.

When do I need to run a full code verification loop with CI quality gates?▼

A full code verification loop is needed when preparing features, refactors, or pre-PR quality gates to ensure repository changes compile and pass all checks.