browser-verify

Drive Chrome via CDP to execute JavaScript and capture UI evidence.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill browser-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-verify
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/browser-verify
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill browser-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It eliminates unreliable, “looks-right” manual checking by letting you inspect and drive a real Chrome browser to validate UI behavior, state, and styling.

Core Features & Use Cases

  • Run arbitrary JavaScript + inspect the results: evaluate page state, extract HTML/text, and check computed CSS, meta, and performance signals.
  • Verify via real user-like input events: click, type, hover, scroll, upload, and drag using Chrome DevTools Protocol Input events instead of synthetic DOM actions.
  • QA-grade checks: capture screenshots/PDFs, read cookies and storage, audit accessibility with axe-core, and review network/performance.

Quick Start

Start Chrome, then run the browser checks by navigating to your target URL and executing the required UI interactions and inspections with the CDP command runner in scripts.

Frequently Asked Questions about browser-verify

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

FAQPage Schema
How do I automate Chrome browser verification for UI testing?

Chrome browser verification is automated by launching a DevTools Protocol client to execute JavaScript, capture screenshots, and simulate real mouse and keyboard input events for deterministic UI testing.

Can I inspect computed CSS styles and DOM elements using Chrome DevTools Protocol?

Yes, Chrome DevTools Protocol allows DOM inspection by executing arbitrary JavaScript to extract HTML text, read computed CSS styles, and check meta tags and page state directly during QA verification.

How do I simulate real user interactions like clicks and typing for QA testing?

Real user interactions are simulated using Chrome DevTools Protocol Input events to click, type, hover, scroll, upload, and drag, replacing unreliable synthetic DOM actions for accurate QA verification.

Do I need npm dependencies to run browser automation with Chrome DevTools Protocol?

No npm dependencies are required. The browser verification tool needs only Chrome or Chromium plus Node 22+, providing a standalone DevTools Protocol client with scripts for launching and stabilizing Chrome.

What's the best way to capture UI evidence like screenshots during automated testing?

Capturing UI evidence is handled by the DevTools Protocol client, which generates screenshots and PDFs while running interaction-driven flows like logins and form verification for QA-grade checks.

Can I audit accessibility and network performance using browser automation?

Yes, browser automation supports accessibility audits using axe-core and network performance reporting, alongside reading cookies and storage, to provide comprehensive QA verification for web UIs.