Verified:GitHub

site-verify

Verify full-stack user journeys for 404s, console errors, and network failures.

Updated Aug 27, 2026

Search Tags:#Docker #end-to-end testing #QA automation #Chrome DevTools MCP #site verification #backend validation #network debugging

Ready to run

npx skills add https://github.com/krazyuniks/guitar-tone-shootout-archive --skill site-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: site-verify
Source: https://github.com/krazyuniks/guitar-tone-shootout-archive/tree/main/.claude/skills/site-verify
Command: npx skills add https://github.com/krazyuniks/guitar-tone-shootout-archive --skill site-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables end-to-end verification of a user's journey across a full-stack environment, enabling detection of 404s, console errors, network failures, and database state inconsistencies during development.

Core Features & Use Cases

End-to-end Verification: Validate complete user journeys from public access through authentication to data-driven pages.
MCP-Powered Observability: Use Chrome DevTools MCP to capture snapshots, list console messages, and inspect network traffic.
DB & State Validation: Verify backend state matches expectations after each step and surface issues for quick remediation.

Quick Start

Start the site verification workflow by spinning up services, connecting MCP, and walking through the defined user journey steps. Then use the MCP commands to take snapshots, inspect console logs, and check network requests as you progress.

Frequently Asked Questions about site-verify

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

FAQPage Schema

How do I verify end-to-end user journeys and catch database state mismatches?▼

End-to-end user journey verification checks full-stack flows for 404s, console errors, network failures, and database state mismatches. By using Chrome DevTools MCP, you can capture snapshots and inspect network traffic to validate backend state against expectations after each step.

Does end-to-end QA automation require Docker-based services and Chrome DevTools MCP?▼

Yes, end-to-end QA automation for site verification requires Docker-based services and Chrome DevTools MCP connectivity. These dependencies are necessary to run reproducible, reportable checks against a running backend and perform MCP-driven network debugging.

How do I inspect network traffic and console errors during full-stack development?▼

To inspect network traffic and console errors during full-stack development, use Chrome DevTools MCP to capture snapshots and list console messages. This allows you to monitor public and authenticated pages, surfacing issues for quick remediation during multi-step journeys.

What is the best way to automate backend validation for authenticated pages?▼

Automating backend validation for authenticated pages is best achieved through MCP-driven checks run against a running backend. This approach validates complete user journeys, ensuring backend state matches expectations and catching network failures reproducibly.

Can I use site verification commands for multi-step journeys in QA scenarios?▼

Yes, you can use site verification commands for multi-step journeys in QA scenarios. The prescribed verification commands apply to development and QA scenarios, enabling you to walk through defined user journey steps and validate data-driven pages.

Why does end-to-end site verification fail to catch console errors without MCP connectivity?▼

End-to-end site verification fails to catch console errors without MCP connectivity because Chrome DevTools MCP provides the required observability. It powers the capture of snapshots and the listing of console messages needed to surface issues during full-stack flows.