verification-loop

Run build, type-check, lint, tests, security scans, and diff review for PR readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or risky changes from slipping into a Claude Code workflow by enforcing consistent build, type, lint, test, security, and diff review checks.

Core Features & Use Cases

  • Multi-phase quality gates: Runs build, type checking, linting, tests (with coverage expectations), security scanning, and a diff-focused review so issues are caught before PRs.
  • PR readiness reporting: Produces a single verification report with pass/fail status and an overall READY/NOT READY decision.
  • Use Case: After completing a feature or refactor, run the full verification loop to confirm everything still builds, is type-correct, passes lint/tests, has no obvious security red flags, and that the diff matches intent.

Quick Start

Run the verification-loop skill after your changes and respond with a filled verification report indicating READY or NOT READY 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 a pre-PR check for build, lint, and test coverage in one step?

A pre-PR check runs build, type-check, lint, tests, security scans, and diff review together to catch regressions. This produces a structured verification report with pass/fail error counts and a PR readiness decision.

What is the best way to automate code review and security scanning before merging?

Automated code review scans git diffs for unintended changes and checks for secrets or obvious security issues. Summarizing these results helps prevent broken or risky changes from slipping into a workflow.

How do I check if my code changes are ready for a pull request?

To check pull request readiness, run a full verification loop after completing a feature or refactor. It outputs an overall READY or NOT READY decision based on build status, type correctness, lint, tests, and security scans.

Does verification-loop work without external CI dependencies?

Yes, the verification loop works without external dependencies. It applies directly to code sessions to enforce consistent build, type, lint, test, security, and diff review checks locally before CI.

Why does my code pass linting but fail the overall PR readiness check?

PR readiness checks evaluate multiple phases simultaneously. Code can pass linting but fail overall readiness if type checking, tests with coverage expectations, security scans, or diff reviews detect failures.

When do I need to run a full quality gate on my code changes?

You need a full quality gate after refactors, feature completion, and pre-PR checks. Running build, type-check, lint, test, security scan, and diff review ensures everything still builds and matches intent before merging.