verification

Run tests, measure coverage, and validate acceptance criteria for software releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal validation workflow for software releases by executing tests, measuring coverage, and validating acceptance criteria during the T stage, reducing release risk.

Core Features & Use Cases

  • Automatically run the test suite across projects and report results.
  • Measure and verify test coverage against configured thresholds, and surface gaps.
  • Validate acceptance criteria and generate a concise evidence packet for audits and compliance.

Quick Start

Run the verification workflow and inspect the generated .ai_state/quality.md for results.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I automate test execution and coverage checks in a CI pipeline?

Automate T-stage software verification by running tests, measuring coverage, and validating acceptance criteria within CI pipelines. It generates deterministic test runs, enforces configured coverage thresholds, and outputs audit-ready evidence packets for release workflows.

What is T-stage verification in software release workflows?

T-stage verification is a formal validation workflow that executes test suites, measures coverage gaps, and validates acceptance criteria before release. It reduces release risk by enforcing deterministic pass/fail criteria and generating concise evidence packets for compliance audits.

How do I generate audit-ready reports for test runs and acceptance criteria?

Generate audit-ready reports by running the verification workflow to validate acceptance criteria and measure test coverage. The process produces a concise evidence packet stored in the .ai_state/quality.md file, satisfying functional requirements for compliance and audit reviews.

Does this verification process work across different programming languages?

Yes, the verification process applies to software projects across multiple languages by focusing on standard test execution, coverage measurement, and acceptance validation. It provides language-agnostic guardrails and clear pass/fail criteria for CI pipelines and release workflows.

How do I enforce minimum test coverage thresholds before a software release?

Enforce minimum test coverage by configuring threshold values within the verification workflow. The process measures coverage during T-stage validation, surfaces gaps if thresholds are not met, and applies clear pass/fail guardrails to block non-compliant releases.

Can I validate acceptance criteria automatically during continuous integration?

Yes, you can validate acceptance criteria automatically during continuous integration by integrating the T-stage verification workflow. It checks project requirements, executes deterministic test runs, and generates an evidence packet to ensure release readiness and compliance.