verification

Infer user stories from code changes and verify browser-to-API-to-data flows.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/esneiderbravo/hackaton --skill verification-esneiderbravo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/esneiderbravo/hackaton/tree/main/.github/skills/verification
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill verification-esneiderbravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates end-to-end verification by inferring the intended user story from the codebase and validating the complete flow across browser, API, and data sources.

Core Features & Use Cases

  • Infers the intended user flow from code changes and validates the entire journey (UI → API → data → response).
  • Triggers on dev server startup or when issues are reported, collecting evidence and presenting a structured verification report.
  • Supports boundary checks, evidence gathering, and integration with environment, routing, and middleware signals for comprehensive validation.

Quick Start

Start your dev server and prompt the verifier to run an end-to-end check for the current build.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify end-to-end user flows from UI to data after code changes?

End-to-end user flow verification is performed by inferring the intended user story from code changes and validating the complete journey from browser to API to data and response. Evidence is collected and structured into a verification report.

What is the best way to automate end-to-end testing on dev server startup?

Automated end-to-end testing on dev server startup is triggered by inferring the intended user flow from the codebase and validating the entire UI to data journey. Boundary checks and integration signals are evaluated to provide actionable insights.

How does data-flow verification work for browser and API requests?

Data-flow verification for browser and API requests works by validating request handling, data sources, and routing middleware. It enforces structured verification by checking the complete flow and offering guidance for environment variables and AI integrations.

Can I use end-to-end verification to check routing middleware and environment variables?

Yes, end-to-end verification can check routing middleware and environment variables. It enforces structured verification by validating request handling and data sources, while offering chain-to guidance for routing, environment variables, and AI integrations.

When should I run end-to-end flow checks during development?

End-to-end flow checks should be run during development on dev server startup or when users report issues. Triggering verifications at these boundaries gathers evidence and reports actionable insights for the current build.

Why are my API and data response boundaries failing during end-to-end verification?

API and data response boundaries may fail during end-to-end verification due to misconfigured request handling, data sources, or routing middleware. The verification process gathers evidence and reports these boundaries with actionable insights.