verification-loop

Run a six-phase verification workflow for JavaScript/TypeScript and Python projects.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/BuildSmarterAI/claude-skills --skill verification-loop-buildsmarterai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/BuildSmarterAI/claude-skills/tree/main/verification-loop
Command: npx skills add https://github.com/BuildSmarterAI/claude-skills --skill verification-loop-buildsmarterai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the verification of Claude Code sessions to catch defects before they reach pull requests or production.

Core Features & Use Cases

  • Build Verification: Ensure the project builds successfully across environments.
  • Type Check: Validate TypeScript and Python type correctness to prevent type errors.
  • Lint Check: Enforce coding standards and detect code quality issues.
  • Test Suite: Run tests with coverage and report results for quality gates.
  • Security Scan: Scan for secrets and risky patterns to reduce exposure.
  • Diff Review: Review changes to identify unintended edits and edge cases.

Use cases include: after feature completion, before PR creation, and after refactoring to verify end-to-end health.

Quick Start

Run /verify after completing a feature or significant change to generate a full verification report.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run code verification checks before creating a pull request?

Code verification before a PR involves running builds, type checks, lint, tests, and security scans. This Skill automates that workflow by executing a six-phase validation process and generating a structured report to ensure changes are ready for review.

What is included in an end-to-end code verification workflow?

An end-to-end verification workflow includes build validation, type checking, lint enforcement, test execution, security scanning for risky patterns, and diff review. These phases confirm code correctness and prevent unintended edits before integration.

Can I use automated lint and type checking for both JavaScript and Python projects?

Yes, automated lint and type checking can be applied to both JavaScript/TypeScript and Python projects. The verification process validates type correctness and enforces coding standards across these environments to prevent type errors and quality issues.

How do I scan my codebase for security risks and secrets before submitting changes?

Scanning for security risks before submitting changes requires running a dedicated security check phase. This process identifies secrets and risky patterns in the codebase, reducing exposure before the code reaches production or pull requests.

What's the best way to verify code health after completing a refactoring session?

The best way to verify code health after refactoring is to run a structured validation workflow that checks builds, types, lint, tests, and security. This confirms that the structural changes did not introduce regressions or break existing functionality.