verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill verification-loop-bennybennison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/verification-loop
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill verification-loop-bennybennison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken or low-quality changes from entering the codebase by enforcing a sequential verification pipeline that catches build failures, type errors, lint issues, failing tests, security problems, and unintended diffs before committing or opening a PR.

Core Features & Use Cases

  • Sequential Verification Phases: Run Build, Type Check, Lint, Tests, Security Scan, and Diff Review in order and stop on failure.
  • Multi-language Support: Examples and commands provided for Python and TypeScript workflows (py_compile/mypy/ruff/pytest and npm/tsc/lint/npm test).
  • Developer Workflow Integration: Use after completing a feature, before creating a PR, after refactors, or periodically during long sessions to prevent regression accumulation.

Quick Start

Run the verification loop at a checkpoint by executing the build, type check, lint, tests, security scan, and diff review before creating a PR or committing changes.

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-commit checks for Python and TypeScript projects?

Run a sequential verification pipeline covering builds, type checks, linting, tests, security scans, and diff reviews before committing. This pipeline integrates standard toolchains like python, npm, mypy, tsc, ruff, eslint, and pytest to catch issues early.

What is the best way to prevent broken code from entering a pull request?

Prevent broken code by applying a sequential verification pipeline that stops on failure during build, type check, lint, test, security scan, and diff review phases. This enforces code quality gates before opening a pull request.

Can I use mypy and tsc type checkers in a continuous integration verification loop?

Yes, the verification pipeline requires standard toolchains including type checkers like mypy for Python and tsc for TypeScript. It applies these type checking phases sequentially to validate code before committing or opening a pull request.

How do I automate linting and security scans before creating a git commit?

Automate linting and security scans by running a sequential verification loop that executes ruff or eslint followed by a security scan phase. The pipeline stops on failure to ensure no low-quality changes enter the commit.

When do I need to run a verification pipeline during a long development session?

Run the verification pipeline periodically during long sessions to prevent regression accumulation. It validates builds, type errors, lint issues, tests, and unintended diffs at checkpoints before finalizing your feature or refactor.

Does the pre-commit verification loop work with both pytest and npm test runners?

Yes, the verification loop requires standard test runners including pytest for Python and npm test for TypeScript. It executes these test phases sequentially to catch failing tests before committing changes or opening pull requests.