verification-loop

Execute build, typecheck, lint, test, and security checks for Claude Code sessions.

Updated Mar 1, 2026

Search Tags:#security #verification #build #code-quality #lint #tests #typecheck

Ready to run

npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill verification-loop-derekhu0002

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/derekhu0002/ai4pb-orchestrator/tree/main/.agents/skills/verification-loop
Command: npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill verification-loop-derekhu0002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes the verification of Claude Code sessions by ensuring builds, type checks, linting, tests, and security scans are executed before changes are merged or deployed.

Core Features & Use Cases

End-to-end verification pipeline covering Build Verification, Type Check, Lint Check, Test Suite, and Security Scan.
Use cases include post-feature completion, PR pre-checks, and post-refactor validation to prevent regressions.
Deterministic, repeatable verification with clear pass/fail criteria and actionable reports for developers and reviewers.

Quick Start

Run the verification workflow on the current project to execute build, type checks, lint, tests, and security scans.

Frequently Asked Questions about verification-loop

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

FAQPage Schema

How do I automate build, typecheck, lint, test, and security scans before a pull request?▼

Automated end-to-end verification executes build, typecheck, lint, test, and security scans in a deterministic pipeline before pull requests. It enforces clear pass/fail criteria and generates actionable reports for reviewers to prevent regressions.

What is an end-to-end verification pipeline for code sessions?▼

An end-to-end verification pipeline standardizes code quality checks by sequentially running builds, type checks, linting, tests, and security scans. It ensures deterministic, repeatable validation with clear exit statuses after feature completion or refactoring.

When should I run code quality and security verification checks?▼

Run code quality and security verification checks after feature completion, before pull requests, and after refactoring. This prevents regressions by ensuring all changes pass build, typecheck, lint, test, and security scans before merging.

Can I use automated verification to prevent regressions after refactoring?▼

Yes, automated verification prevents regressions after refactoring by executing a deterministic pipeline of build, typecheck, lint, test, and security scans. It produces detailed reports suitable for archival and PR review.

Does the verification pipeline generate reports for PR review?▼

Yes, the verification pipeline generates detailed, actionable reports suitable for PR review and archival. It provides deterministic pass/fail results across build, typecheck, lint, test, and security stages.

What's the best way to standardize security and lint checks across development sessions?▼

Standardize security and lint checks by enforcing a deterministic verification pipeline that covers build, typecheck, lint, test, and security scans. This ensures repeatable validation with clear exit statuses across all sessions.