verification-loop

Runs a six-phase verification pipeline covering build, type check, lint, tests, security, and diff review.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill verification-loop-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/NalinDalal/skillset/tree/main/skills/engineering/verification-loop
Command: npx skills add https://github.com/NalinDalal/skillset --skill verification-loop-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often reach pull requests without systematic validation, letting type errors, lint violations, failing tests, or security vulnerabilities slip into main branches. This Skill enforces a strict six-phase gate where each phase must pass before the next runs. ## Core Features & Use Cases - Six Sequential Phases: Build, Type Check, Lint, Test Suite, Security Scan, and Diff Review, each with explicit pass criteria and failure stops. - Verification Report Generation: Produces a structured Markdown report with per-phase status, duration, and coverage thresholds (lines >= 80%, branches >= 70%). - CI Automation: Includes a ready-to-adapt GitHub Actions workflow that runs all phases on pull requests. - Use Case: Before opening a PR for a new authentication feature, run the loop to confirm the build compiles, types are strict-clean, tests meet coverage thresholds, no secrets are hardcoded, and the diff stays under 400 lines. ## Quick Start Run the full verification loop on my current branch and generate a verification report before I open the 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 verify code before creating a pull request?▼

Run the six phases in order: build, type check, lint, test suite with coverage, security scan, and diff review. Each phase must pass before the next starts, and any failure stops the loop until fixed.

What should a CI verification pipeline include?▼

A verification pipeline should include compilation, static type checking, linting, automated tests with coverage thresholds, dependency vulnerability audits, and diff scope review. The Skill provides a GitHub Actions workflow implementing all six phases.

What test coverage thresholds should I enforce?▼

The recommended thresholds are lines >= 80%, functions >= 80%, branches >= 70%, and statements >= 80%. Tests run with bun test --coverage, and the loop fails if any threshold is not met.

How do I detect hardcoded secrets in code before merging?▼

Use grep to scan source files for patterns like password, secret, token, key, and api_key, and check the diff for sensitive filenames such as .env. Combine this with bun audit --audit-level=high to catch vulnerable dependencies.

When should I not run the full verification loop?▼

Skip the full loop for trivial changes like typo fixes or documentation-only edits where build and test phases add no signal. It is designed for pre-PR validation, major changes, and releases.