verification

Verifies full-stack user flows end-to-end across browser, API, data, and response layers.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sharad07072007/paras --skill verification-sharad07072007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/sharad07072007/paras/tree/main/.agents/plugins/vercel/skills/verification
Command: npx skills add https://github.com/sharad07072007/paras --skill verification-sharad07072007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature "almost works" or something feels off, developers often check only one layer and miss where the flow actually breaks. This Skill infers the complete user story being built and verifies every boundary — browser, server, API route, data source, and response rendering — with concrete evidence instead of guesswork. ## Core Features & Use Cases - Story Inference: Reads recently edited files, routes, and environment files to state the exact user story before checking anything. - Multi-Layer Evidence Gathering: Inspects browser console, dev server terminal, runtime logs, and environment variables, reporting findings at each layer. - Data Flow Tracing: Walks the path from UI trigger through API handler to external dependencies and back, catching common breaks like missing awaits, wrong HTTP methods, and absent env vars. - Use Case: After starting a Next.js dev server, ask whether the new checkout feature works — the Skill traces the button click, the POST to the API route, the database call, and the rendered response, then reports exactly which boundary fails and how to fix it. ## Quick Start Ask the assistant to verify that the feature you just built works end to end across the browser, API, and database.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify a full-stack feature works end to end?

End-to-end verification traces the flow from the UI trigger through the API route to the data source and back to the rendered response. This Skill checks each boundary with evidence from the browser console, server logs, and environment configuration, then reports the first broken layer with a fix.

Why does my app work locally but fail after deployment?

A common cause is environment variables present in .env.local but missing in the deployed runtime. Verification compares expected versus actual env vars using vercel env ls and checks runtime logs to identify the mismatch.

What are common breaks between a client fetch and an API route?

Frequent breaks include wrong HTTP methods, missing await on async calls, URL or payload mismatches, and importing server modules into client components. The Skill checks the fetch call against the route handler to catch these.

Does this replace unit tests or Playwright tests?

No. This Skill performs investigative full-story verification of a feature flow, not automated test suites. It explicitly excludes unit test, Jest, Vitest, Playwright, and Cypress workflows and focuses on diagnosing why a feature is not working.

When should I stop debugging a broken flow?

Stop at the first confirmed broken boundary and report it with evidence and a specific fix rather than continuing past it. Also stop when two consecutive layers return no useful signal, which indicates an observability gap requiring added logging.