One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill verification-loop-eotel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/verification-loop
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill verification-loop-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a robust, automated pre-PR verification workflow that ensures builds, type checks, lint, tests, and security checks succeed before merging.

Core Features & Use Cases

  • Phase 1: Build Verification — Check if the project builds using npm run build or pnpm build; if the build fails, stop and fix before continuing.
  • Phase 2: Type Check — For TypeScript projects, run tsc --noEmit; for Python projects, run pyright; report all type errors and fix critical ones before continuing.
  • Phase 3: Lint Check — Run lint for JavaScript/TypeScript with npm run lint and for Python with ruff check.
  • Phase 4: Test Suite — Run tests with coverage and report total, passed, failed, and coverage percentage; enforce a minimum threshold (e.g., 80%).
  • Phase 5: Security Scan — Scan for secrets and sensitive patterns and flag potential exposures.
  • Phase 6: Diff Review — Review git diffs to catch unintended changes and edge cases. This section outlines a deterministic sequence to validate changes before PR creation.

Output Format

After running all phases, produce a verification report that summarizes Build, Types, Lint, Tests, Security, Diff, and Overall readiness; include any issues to fix.

Quick Start

Run the verification loop on your codebase to kick off the predefined phases and verify readiness for PR.

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-merge checks for build, lint, type checks, and tests?

Pre-merge checks coordinate build, type check, lint, test, and security scan phases in a deterministic sequence to validate changes before PR creation. This orchestration runs tools like tsc, ruff, and npm to produce a final verification readiness report.

Can I use this pre-PR verification workflow for both Python and TypeScript projects?

Yes, pre-PR verification works for both Python and TypeScript projects. The workflow orchestrates tsc and npm run lint for JavaScript/TypeScript, alongside pyright and ruff check for Python, adapting its type check and lint phases to the detected environment.

What is the best way to automate security scans and diff reviews before creating a pull request?

Automating security scans and diff reviews before a pull request is best handled by a phased verification loop that scans for secrets, flags sensitive patterns, and reviews git diffs to catch unintended changes, summarizing findings in a concise readiness report.

How do I enforce a minimum test coverage threshold during pre-merge validation?

To enforce a minimum test coverage threshold during pre-merge validation, the test suite phase runs tests with coverage reporting, enforcing a minimum threshold such as 80% and reporting total, passed, and failed counts before allowing the PR process to continue.

What happens if the build fails during the automated pre-PR verification sequence?

If the build fails during the automated pre-PR verification sequence, the workflow stops immediately. The build verification phase requires a successful npm or pnpm build before proceeding to subsequent type check, lint, test, and security phases.

Does pre-merge type checking run pyright and tsc automatically?

Yes, pre-merge type checking automatically runs tsc --noEmit for TypeScript projects and pyright for Python projects. The phase reports all type errors and requires fixing critical ones before continuing to the lint check phase.