Verify end-to-end user flows across browser, server, API, and data layers.
npx skills add https://github.com/rauell1/safaricharge --skill verification-rauell1
Please help me install this Agent Skill. Skill: verification Source: https://github.com/rauell1/safaricharge/tree/main/.agents/skills/verification Command: npx skills add https://github.com/rauell1/safaricharge --skill verification-rauell1
This Skill helps you confirm whether an application actually works end to end, instead of checking only a single component or screenshot. It is designed for moments when a feature is broken, uncertain, or needs a full-flow proof across the browser, server, data, and environment.
Ask the verification skill to infer the feature flow and verify the browser, server, API, data, and environment end to end.
High-intent search queries and answers about installing and using this skill.
To verify an end-to-end user flow, you trace the complete path from browser interaction to server response, checking browser behavior, server logs, API routes, and data sources together. This full-stack validation requires evidence at each boundary and stops at the first confirmed failure.
A dev server fails full-stack validation when a specific boundary breaks across the browser, server, API, data, or environment. Cross-layer verification identifies the exact layer of failure, provides evidence, and reports the likely fix instead of just checking a single component.
Boundary-focused debugging is the process of checking request methods, payloads, async handling, and response shapes across application layers. It stops at the first confirmed break, reporting the exact layer, evidence, and likely fix rather than testing the entire flow blindly.
Debug broken features by running cross-layer verification that checks browser behavior, server logs, API routes, data sources, and environment variables simultaneously. This identifies the user story flow and isolates the exact failure point across the full stack.
Yes, you can validate new login, dashboard, or payment features by verifying the complete end-to-end user flow. This involves inferring the feature flow, mapping the UI entry point to the API, and validating data rendering and environment configuration.
You need end-to-end verification when a feature is broken, uncertain, or requires full-flow proof before shipping. It confirms whether the application actually works across the browser, server, data, and environment, rather than relying on isolated component checks or screenshots.
esneiderbravoInfer user stories from code changes and verify browser-to-API-to-data flows.
EvanZhang008Orchestrate Playwright, API, and unit tests to verify Walnut features end-to-end.
pynbj1001Launch Playwright browser automation to capture console logs, network activity, and errors.
Logos-LiberDefine and enforce full-stack coding conventions and design patterns.
