browser-verification

Automate browser verification of UI changes with Playwright to detect visual regressions and runtime errors.

8|2|Updated Jan 15, 2026

Search Tags:#workflow #verification #playwright #ui-testing #quality-assurance #browser

Ready to run

npx skills add https://github.com/srstomp/pokayokay --skill browser-verification-srstomp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-verification
Source: https://github.com/srstomp/pokayokay/tree/main/plugins/pokayokay/skills/browser-verification
Command: npx skills add https://github.com/srstomp/pokayokay --skill browser-verification-srstomp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically verify UI changes in a real browser after implementation, catching visual regressions and runtime errors before code review.

Core Features & Use Cases

Integrated into the /work workflow to validate UI changes after implementation.
Performs visual checks, interaction testing, and console error detection using Playwright.
Helps prevent CSS issues, runtime JS errors, and layout regressions in production-ready code.

Quick Start

Trigger browser verification after UI changes by executing the work flow step in the /work pipeline.

Frequently Asked Questions about browser-verification

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

FAQPage Schema

How do I verify UI changes in a real browser after implementation?▼

Browser verification automates UI verification in real browsers using Playwright to detect visual regressions and runtime errors after code changes. It performs visual checks, interaction testing, and console error detection to prevent CSS and layout issues before code review.

What is browser verification for visual regressions?▼

Browser verification is an automated process that validates UI changes in real browsers to catch visual regressions and runtime JavaScript errors. It uses Playwright to execute visual checks and interaction tests, ensuring layout and component integrity before production.

Do I need a dev server running to use Playwright for UI testing?▼

Yes, browser verification requires a dev server or an accessible rendering environment to operate. Playwright automates the browser against this running environment to validate UI components and detect runtime errors during the workflow.

How do I run browser verification within the work workflow?▼

You trigger browser verification by executing the work flow step in the work pipeline after making UI changes. This integrated step automatically leverages Playwright to validate layouts, components, and interactions across real browsers.

Can I use this to check for runtime JavaScript errors and CSS issues?▼

Yes, browser verification detects runtime JavaScript errors and CSS issues by performing visual checks and console error detection. It leverages Playwright to automate interactions and catch layout regressions in the rendered output.

What are the limitations of automated browser verification for UI changes?▼

Browser verification is limited to detecting visual regressions, runtime JavaScript errors, and CSS issues within an accessible dev server environment. It operates within the work workflow and requires a running rendering environment to execute Playwright checks.