skills.rest
opslane
opslaneOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verify

Automate frontend change verification against acceptance criteria via Playwright MCP.

114|3|Updated Mar 9, 2026
Search Tags:#automation#frontend#qa#verification#mcp#spec#playwright
One-click install
npx skills add https://github.com/opslane/opslane --skill verify-opslane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/opslane/opslane/tree/main/skills/verify
Command: npx skills add https://github.com/opslane/opslane --skill verify-opslane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies frontend changes against formal acceptance criteria by driving a real browser through Playwright MCP and reporting outcomes, ensuring UI behavior aligns with specs before PRs are merged.

Core Features & Use Cases

  • Converts spec acceptance criteria into automated UI checks against a running app.
  • Captures per-AC evidence (video, traces, screenshots) for audit and debugging.
  • Handles preflight steps like dev server readiness and optional authentication as part of the verification flow.

Quick Start

Run /verify in Claude Code to start automated spec verification against your dev server.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate frontend change verification against acceptance criteria?▼

Automate frontend change verification by driving a real browser through Playwright MCP to validate UI behavior against spec acceptance criteria and report outcomes. It ensures UI behavior aligns with specs before PRs are merged.

What do I need to run automated spec verification with Playwright MCP?▼

To run automated spec verification, you need Playwright MCP installed, a running dev server, and an SKILL-specific workflow to index routes and selectors to generate grounded checks.

Can I verify UI behavior across routes and authentication during local development?▼

Yes, you can verify UI behavior across routes, authentication, and dynamic content during local development by applying the verification workflow to validate changes against your running app.

How are verification results captured for auditing and debugging?▼

Verification results are captured by collecting per-acceptance-criteria evidence including video, traces, and screenshots, providing concrete artifacts for audit and debugging purposes.

Does automated UI verification handle dev server readiness and authentication?▼

Yes, automated UI verification handles preflight steps like dev server readiness and optional authentication as part of the overall verification flow before running spec checks.

What is the best way to validate frontend changes before merging a PR?▼

The best way to validate frontend changes before merging is converting spec acceptance criteria into automated UI checks against a running app, capturing evidence to ensure alignment before PR merge.

Related Skills

Explore More Software Engineering Skills→
vercelvercel
246

agent-browser-verify

Automate visual verification of dev servers by checking page load, console errors, and UI elements.

Official
Intermediate
Andreicr1Andreicr1

ce-demo-reel

Capture product behavior as GIFs, terminal recordings, or screenshots and publish public links.

Community
Intermediate
neonwattyneonwatty
23

browser-workflow-to-playwright

Converts browser workflow markdown into Playwright end-to-end tests.

Community
Advanced
crsieblercrsiebler
1

dev-browser

Control a Chrome browser to validate frontend features via manual UI interactions.

Community
Intermediate