verify

Automate post-build verification across code, database, API, and UI layers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/The-Entourage-AI-Development/trade-certify --skill verify-the-entourage-ai-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/The-Entourage-AI-Development/trade-certify/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/The-Entourage-AI-Development/trade-certify --skill verify-the-entourage-ai-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures end-to-end quality across code, database, API, and UI by validating changes before deployment, reducing regressions and drift.

Core Features & Use Cases

  • Multi-layer verification: static analysis, database schema checks, API/tRPC validation, and visual/browser testing.
  • Auto-scope: detects relevant changes from git diff and runs only impacted layers to speed up feedback.
  • Rich reporting: outputs pass/fail results with actionable remediation recommendations.

Quick Start

Run the verify skill to automatically validate recent changes across all four layers and surface a unified report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate post-build verification across my database, API, and UI layers?

Post-build verification is automated by executing a four-layer pipeline that applies static analysis, read-only database schema checks, API convention validation, and visual route testing to detect code regressions and drift before deployment.

What is database drift detection and when do I need to check for it in CI/CD?

Database drift detection validates schema changes against expected states using read-only database checks. It is needed during CI/CD pipelines to catch discrepancies caused by code changes before they reach production.

How do I run end-to-end UI route testing automatically from git diffs?

Visual UI route testing runs automatically by auto-scoping git diffs to detect changed files, triggering a browser agent to test only impacted routes and surface broken navigation without manual configuration.

Can I perform read-only database schema checks without risking data modification?

Read-only database schema checks validate structural drift and schema integrity without executing write operations, ensuring your database remains untouched while detecting discrepancies from code changes during CI/CD.

What is the best way to validate tRPC API endpoint discrepancies after a build?

Validating API endpoint discrepancies is best handled by applying automated API convention checks during post-build verification to detect mismatches and regressions from recent code changes before deployment.

Why does running all static analysis and UI tests take so long and can I scope them?

Running all verification layers is slow because it checks everything, but you can scope checks by auto-detecting relevant changes from git diffs to run only impacted layers, significantly speeding up feedback.