Opslane
Opslane is self-serve QA for your PR. You paste the ticket; Verify drives a real browser against your local dev server, checks each acceptance criterion, and reports pass/fail with screenshots — inline in Claude Code, before you push.
How it works
When you finish a feature and run /verify, it doesn't just lint the code. It reads the ticket, extracts the concrete acceptance criteria, and asks you about anything ambiguous. Then it drives the actual app via Playwright MCP — clicking, typing, navigating like a person would — and checks each AC against what it sees. You get a per-AC verdict with screenshots, and a Playwright video + trace on anything that didn't pass.
This is the sanity pass you'd otherwise do manually with the PM ticket open in one tab and your dev server in another. It runs locally, against your real app, with no test code to write and no CI to wire up.
Demo
Demo
Installation
Prerequisites: Claude Code with OAuth login (claude login).
In Claude Code, register the marketplace first:
/plugin marketplace add opslane/verify
Then install the plugin:
/plugin install opslane-verify@opslane-verify-marketplace
That's it. The plugin registers two slash commands — /verify-setup and /verify — and wires up the Playwright MCP server automatically. No separate claude mcp add step.
Setup: /verify-setup
Run this once per repo from your repo root, with your dev server running:
/verify-setup
It does the following inline (no npm install, no CLI binary):
- Scaffolds
.verify/ in your repo and adds it to .gitignore if missing.
- Detects your dev server port by reading
package.json scripts (dev/start/serve flags), then .env* files, then framework configs (vite.config.*, next.config.*). Falls back to 3000 and tells you. If it picks the wrong one, you can correct it (e.g. "my dev server runs on 5173").
- Pings the dev server at the detected port. If it can't reach it, it stops here and tells you to start the server first.
- Writes
.verify/config.json with the resolved baseUrl.
- Indexes your routes. Walks your codebase looking for user-facing pages — works for Next.js (
app/, pages/), Remix (routes/), React Router (<Route> / createBrowserRouter), SvelteKit (routes/), Nuxt (pages/), and Express/Hono/Fastify route definitions. Skips /api/*. Handles monorepos.
- Indexes your selectors by reading any existing Playwright (
*.spec.ts) or Cypress (*.cy.ts) tests and extracting the URLs they navigate to and the selectors they use. Prefers data-testid and role-based selectors.
- Writes
.verify/app.json — a single JSON map of routes + per-page selectors that /verify reads later for grounded AC extraction.
- Confirms Playwright MCP is registered and prints a setup summary.
Re-run /verify-setup any time your routes change or you've added new tests — the index gets refreshed.
Running: /verify
Once setup is done, verify any change with:
/verify # auto-discovers a likely spec file
/verify path/to/spec.md # or point it at a specific spec
Here's what happens, turn by turn:
