verify-setup

Name: verify-setup
Availability: InStock
Author: Opslane

Automate Claude Code /verify setup by detecting the dev server and indexing routes.

114|3|Updated Mar 9, 2026

Search Tags:#automation #dev-server #playwright-mcp #web-app #config-json #verify-setup #routing-indexing

Ready to run

npx skills add https://github.com/opslane/opslane --skill verify-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-setup
Source: https://github.com/opslane/opslane/tree/main/skills/verify-setup
Command: npx skills add https://github.com/opslane/opslane --skill verify-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the one-time setup workflow for Claude Code's /verify by auto-detecting the local dev server and indexing the app.

Core Features & Use Cases

Scaffold a .verify directory, detect the dev server port, and ping the server to ensure it is running.
Index routes and selectors to generate a grounded app.json for use with /verify, and verify Playwright MCP readiness.
Works across common web app frameworks (Next.js, Remix, React Router, SvelteKit, Nuxt, Express) to streamline initial setup and ongoing testing.

Quick Start

Run /verify-setup from your repo root to initialize the verify environment.

Frequently Asked Questions about verify-setup

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

FAQPage Schema

How do I automate route indexing and dev server detection for my web app?▼

You can automate dev server detection and route indexing by running a single setup command from your repository root. This workflow pings the local server, indexes routes and selectors, and generates a grounded app.json for testing.

Does verify-setup work with Next.js, Remix, SvelteKit, Nuxt, and Express?▼

Yes, setup auto-detection works across common frameworks including Next.js, Remix, React Router, SvelteKit, Nuxt, and Express. It applies framework-specific logic to prepare route mappings and element selectors.

How do I configure Playwright MCP readiness for automated web app testing?▼

To configure Playwright MCP readiness, run the setup workflow to validate your configuration. It checks MCP readiness and writes the necessary config.json file to ensure your environment is prepared for automated testing.

What is the best way to scaffold a .verify directory and write config.json?▼

The best way to scaffold a .verify directory is running an automated setup command. It locates the directory, detects the port, pings the server, and writes both config.json and app.json with indexed route data.

Why does my local dev server need to be running before initializing route mappings?▼

Your local dev server must be running because the setup workflow pings the server to ensure it is active before indexing routes. This guarantees accurate route mapping and element selector generation for your application.

Can I index selectors and routes without manually specifying a dev server port?▼

Yes, you can index selectors and routes without manual port specification because the setup workflow auto-detects the local dev server port. It pings the detected port to verify connectivity before writing the app.json file.