dev-verify

Execute acceptance tests and loop fixes until features pass verification.

Updated Jan 1, 2026

Search Tags:#automation #qa #verification #ci-cd #software-testing #acceptance-tests #debug-loop

Ready to run

npx skills add https://github.com/AirMile/claude-config --skill dev-verify-airmile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-verify
Source: https://github.com/AirMile/claude-config/tree/main/skills/dev-verify
Command: npx skills add https://github.com/AirMile/claude-config --skill dev-verify-airmile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial verification — acceptance tests + fix loops. After verify, the code is good. Use with /dev-verify after /dev-build.

Core Features & Use Cases

End-to-end validation of feature readiness through adversarial testing, acceptance criteria, and iterative fixes.
Integration planning: classify tests into COVERED, AUTO, and MANUAL, and map them to acceptance criteria.
Traceable results: maintains session data, backlog status, and feature.json updates to ensure auditability.

Quick Start

Run the verification on a feature by executing /dev-verify {feature-name} after completing /dev-build.

Frequently Asked Questions about dev-verify

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

FAQPage Schema

How do I automate acceptance tests and fix loops for CI-CD verification?▼

You automate adversarial verification by executing acceptance tests and looping code fixes until the feature passes. This handles the end-to-end flow from backlog classification to verified feature readiness, ensuring post-build contract checks are met.

What is adversarial verification in software testing?▼

Adversarial verification is the process of validating feature readiness through acceptance criteria and iterative fix loops. It classifies tests into COVERED, AUTO, and MANUAL categories, mapping them to acceptance criteria to ensure code reliability.

How do I run a verification session after a feature build?▼

You run the verification on a feature by executing the verify command with the feature name after completing your build. This initiates the debug loop, executing tests and applying fixes until all acceptance criteria pass.

Does the verification process maintain traceable results for auditability?▼

Yes, the verification process maintains session data, backlog status, and feature.json updates to ensure auditability. It provides traceable results by documenting the entire testing and debug loop session.

Can I classify tests into different categories during the verification loop?▼

Yes, you can classify tests into COVERED, AUTO, and MANUAL categories during integration planning. The verification process maps these classified tests directly to your defined acceptance criteria.

What should I do if my acceptance tests fail during the debug loop?▼

If acceptance tests fail during the debug loop, the automated verification process continues iterating code fixes against the failures. It loops until the feature passes all post-build contract checks and acceptance criteria.