verify

Run unit, integration, and end-to-end tests and store verdicts under .harness/evidence.

8|1|Updated Mar 22, 2026

Search Tags:#testing #e2e #evidence #verify #unit-tests #integration-tests

Ready to run

npx skills add https://github.com/zxdxjtu/harness --skill verify-zxdxjtu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/zxdxjtu/harness/tree/main/skills/verify
Command: npx skills add https://github.com/zxdxjtu/harness --skill verify-zxdxjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Three-stage verification of a feature from unit tests through integration tests to end-to-end validation, with an organized evidence package for audit and rollback.

Core Features & Use Cases

End-to-end feature validation: V1 unit tests, V2 integration checks, and V3 E2E scenarios to ensure full coverage.
Evidence packaging: automatically generate and store verdicts and results under the .harness/evidence directory for traceability.
CI/CD readiness: integrates into standard test runners and workflows to streamline quality gates.

Quick Start

Run verification for a given feature ID through V1, V2, and V3 and generate the complete evidence package.

Frequently Asked Questions about verify

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

FAQPage Schema

What is end-to-end feature verification across unit, integration, and e2e tests?▼

End-to-end feature verification automates V1 unit tests, V2 integration checks, and V3 E2E scenarios to ensure full coverage. It records results and generates a verdict for audit and rollback decisions.

How do I generate an auditable evidence package for CI/CD test results?▼

To generate an auditable evidence package, run verification for a given feature ID. The process records V1, V2, and V3 results and automatically stores verdicts and results under the .harness/evidence directory.

Can I integrate three-stage verification into standard test runners and CI/CD pipelines?▼

Yes, three-stage verification integrates into standard test runners and CI/CD workflows. It is designed for CI/CD readiness to streamline quality gates and automate feature-level validation.

What's the best way to automate feature-level validation for audit and rollback decisions?▼

Automating feature-level validation involves running V1, V2, and V3 tests to produce per-ARGUMENT results. The system generates a complete evidence package and a final verdict for rollback decisions.

When do I need to store test results under the .harness/evidence directory?▼

You need to store test results under the .harness/evidence directory when performing three-stage verification for traceability. It satisfies the requirement to produce per-ARGUMENT results for audit purposes.

Does end-to-end verification work without external dependencies for unit and integration tests?▼

Yes, end-to-end verification operates without external dependencies. It automates unit, integration, and E2E testing internally and works with standard test runners to generate evidence packages.