verify-impl

Run API tests, DB verifications, and UI automation to produce a unified verification report.

13|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/OmexIT/claude-skills-pack --skill verify-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-impl
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/verify-impl
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill verify-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, python3, docker, psql, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables automated, end-to-end verification of completed implementations by executing API tests, database state checks, and UI automation, producing concrete evidence to validate system behavior.

Core Features & Use Cases

  • End-to-end verification across API, DB, and UI layers using an optional test plan.
  • Auto-discovery of test plans or derivation from specs, with data captured between layers.
  • Evidence generation and consolidated verification reports for audit and traceability.

Quick Start

Run verify-impl to execute the current e2e test plan against your live services and produce a final verification report.

Frequently Asked Questions about verify-impl

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

FAQPage Schema
How do I run end-to-end verification tests against live API and database implementations?

End-to-end verification tests execute API tests, database state checks, and UI automation against live services to produce concrete evidence. The system orchestrates these layers, passes captured data across steps, and generates a consolidated audit report.

Do I need a test plan file to run automated API and UI verification?

No, a predefined test plan is optional for automated API and UI verification. The system supports a spec-to-impl workflow via e2e/test-plan.yaml but automatically falls back to spec-derived tests when no plan exists.

What dependencies are required to execute database and UI automation verifications?

Executing database and UI automation verifications requires curl, jq, python3, docker, and psql. These tools support the orchestration of API tests, database state checks, and UI automation layers.

How does cross-layer data capture work during end-to-end testing?

Cross-layer data capture during end-to-end testing works by orchestrating API, DB, and UI layers sequentially, passing captured data between steps. This ensures that dynamic tokens or database states are verified across the entire implementation.

What is the best way to generate concrete evidence for software implementation audits?

The best way to generate concrete evidence for audits is running automated end-to-end verification that orchestrates API, DB, and UI tests. This process validates system behavior and outputs a unified verification report for traceability.

Can I use this for database state verification alongside API testing?

Yes, you can use this for database state verification alongside API testing. It orchestrates both DB checks using psql and API tests using curl, unifying the results into a single verification report with concrete evidence.