verification-loop

Automates the six-step validator chain to ensure all checks pass before completion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines change delivery by enforcing a verify-fix-verify loop that ensures every change passes all validators before it is considered complete.

Core Features & Use Cases

  • Run the validator chain (check, build, validate:contact-fallbacks, validate:page-structure, validate:design-tokens, audit:site) to verify changes.
  • Identify and fix root causes instead of symptoms to maintain durable quality.
  • Enforce a maximum of five iterations per change to prevent endless loops and ensure timely progress.

Quick Start

Run the verification loop after making a change to ensure all validators pass before completion.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I automate CI gates to ensure code changes pass all validators?

A verification loop automates CI gate checks by running a six-step validator chain and applying fixes iteratively, ensuring all validators pass before a change is considered complete.

What is a verify-fix-verify loop for software quality assurance?

A verify-fix-verify loop for quality assurance runs a six-step validator chain, identifies root causes of failures instead of symptoms, and re-runs validation until all checks pass or five iterations are reached.

How do I run validation checks for page structure and design tokens?

Run validation checks for page structure and design tokens by triggering the automated validator chain, which includes validate:page-structure and validate:design-tokens steps to verify changes during feature updates or bug fixes.

Does the verification loop cap iteration attempts to prevent endless CI cycles?

The verification loop caps iterations at a maximum of five per change to prevent endless validation cycles, ensuring timely progress while enforcing a green pass across all validators before completion.

When do I need to run a site audit validator chain for bug fixes?

Run a site audit validator chain for bug fixes when you need to enforce comprehensive quality assurance, using the audit:site step within the verification loop to identify root causes and verify all changes pass.

Can I use the verification loop for feature updates without manual validation?

Use the verification loop for feature updates to automate validation without manual checks, applying the six-step validator chain during CI gate reviews to ensure all changes pass automatically before completion.