verification

Run multi-mode verification gates with evidence, attempts, and blockers reporting.

3|Updated Mar 25, 2026

Search Tags:#automation #qa #verification #evidence #gate #ci

Ready to run

npx skills add https://github.com/willietran/autoboard --skill verification-willietran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/willietran/autoboard/tree/main/skills/verification
Command: npx skills add https://github.com/willietran/autoboard --skill verification-willietran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification workflows enforce evidence-based QA protocols, ensuring claims are only made after fresh, verifiable results.

Core Features & Use Cases

Light Mode: runs lint, type checks, builds, and tests.
Full Mode: adds dev-server readiness, browser smoke tests, and a coherence audit.
Preflight: assesses tool availability and environment config before sessions.

Quick Start

Run the verify command to trigger the multi-stage QA gate and collect evidence.

Frequently Asked Questions about verification

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

FAQPage Schema

How do I automate evidence-based verification to gate build quality claims?▼

Automate evidence-based verification by running multi-stage QA gates that collect fresh results before gating success. This ensures claims about build quality are strictly validated against verifiable evidence rather than assumptions.

What is the difference between light mode and full mode for CI verification?▼

Light mode verification runs lint, type checks, builds, and tests, while full mode adds dev-server readiness, browser smoke tests, and a coherence audit to provide deeper system validation.

How do I validate environment configuration and tool availability before a QA session?▼

Validate environment configuration and tool availability by running preflight verification. This mode assesses readiness before sessions begin, preventing failures caused by missing dependencies or improper setup.

Does evidence-based QA reporting track verification attempts and blockers?▼

Evidence-based QA reporting strictly tracks verification evidence, attempts, and blockers. This modular approach ensures transparent documentation of what passed, what failed, and what prevented success.

When should I use full system readiness verification instead of lightweight checks?▼

Use full system readiness verification when you need dev-server readiness and browser smoke tests beyond lightweight checks. This ensures comprehensive validation across the entire system architecture before deployment.