verification

Infer and verify end-to-end user stories across browser, API, and data flows.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Moisesjr20/gueclaw --skill verification-moisesjr20
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/Moisesjr20/gueclaw/tree/main/.agents/skills/verification
Command: npx skills add https://github.com/Moisesjr20/gueclaw --skill verification-moisesjr20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.

Core Features & Use Cases

  • Infers user story boundaries across browser, API, and data layers
  • Verifies end-to-end flow with evidence collection and structured reporting
  • Generates actionable guidance when issues are detected

Quick Start

Run verification on the active dev server to validate the end-to-end flow from browser actions to API responses.

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 across browser, API, and data layers?

End-to-end flow verification inspects browser actions, API calls, and data responses to confirm user story integrity. It collects evidence from logs, requests, and environment signals to output a structured verification report detailing the complete flow.

What is the best way to debug why an app feature isn't working on a local dev server?

Debugging why an app feature isn't working is handled by triggering a structured verification workflow on the local dev server. It inspects logs, requests, and responses across the browser-to-data stack to generate actionable guidance for detected issues.

Can I use automated triage to inspect API logs and responses during development?

Automated triage inspects API logs, requests, and responses during local development to verify flow integrity. It applies a structured workflow analyzing environment signals and outputs a detailed report with actionable guidance when issues are detected.

Does end-to-end verification work for UI issues reported during development?

End-to-end verification works for UI issues by inferring user story boundaries from browser actions through to API and data layers. It validates the complete flow on dev servers and generates a structured report with actionable guidance when issues are found.

How do I generate a structured verification report for API and data responses?

Generating a structured verification report involves inspecting API requests, data responses, and environment logs. The verification workflow infers the complete user story, validates the end-to-end flow, and outputs detailed evidence with actionable guidance for any detected issues.

When do I need to run end-to-end flow verification on my application?

End-to-end flow verification is needed when users report issues like 'why isn't this working' or upon dev server start. It confirms flow integrity across browser, API, and data layers by collecting evidence and producing a detailed verification report.