verification-loop

Automate build, type, lint, test, security, and diff checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/overthestream/agent-dotfile --skill verification-loop-overthestream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/overthestream/agent-dotfile/tree/main/general-agentic-utils/skills/verification-loop
Command: npx skills add https://github.com/overthestream/agent-dotfile --skill verification-loop-overthestream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates a six-step verification workflow to ensure code quality before integration, reducing debugging time and the risk of faulty merges.

Core Features & Use Cases

  • Build, Types, Lint, Tests, Security, and Diff steps are executed deterministically to surface issues early.
  • Use Case: before submitting a PR after implementing a feature or refactoring, or after making changes to fix defects.

Quick Start

Run the verification loop by triggering the verify command to automatically run all checks and surface required fixes.

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-PR verification checks for build, types, and tests?

Pre-PR validation is automated by triggering a verify command that executes a six-step workflow covering build, types, lint, tests, security, and diffs to deliver a READY status.

What is end-to-end code verification before submitting a pull request?

End-to-end code verification is an automated six-step workflow executing build, types, lint, tests, security, and diffs to surface integration issues early and ensure code quality.

When should I use automated code verification workflows?

Automated code verification workflows should be used after implementing features, fixing defects, or refactoring to enforce deterministic checks and ensure safe integration before submitting a PR.

Does the verification loop include security and diff checks?

Yes, security and diff checks are included alongside build, types, lint, and tests in the deterministic six-step workflow to deliver a final READY status when all checks pass.

What is the best way to automate type checking and linting before a merge?

Automating type checking and linting is best achieved through a deterministic verification workflow integrating common tooling to execute pre-PR checks and surface issues early.

Do I need specific dependencies to run automated build and test checks?

No specific dependencies are required; the verification workflow integrates with common tooling to enforce deterministic build and test steps, delivering a READY status when all checks pass.