browser-qa

Automate browser-based visual testing and interaction verification for web applications.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill browser-qa-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/browser-qa
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill browser-qa-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based visual testing and interaction verification to catch UI regressions and ensure frontend quality across environments.

Core Features & Use Cases

  • Smoke Test: verify navigation, console errors, and network health.
  • Interaction Test: validate forms, auth flows, and key user journeys across desktop/mobile.
  • Visual Regression: capture and compare screenshots across breakpoints to detect layout shifts.
  • Accessibility: assess keyboard navigation, focus order, and WCAG conformance.

Quick Start

Run browser-qa against your live pages to verify navigation, interactions, and visual stability across breakpoints.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I automate browser testing to catch UI regressions across desktop and mobile viewports?▼

Automated browser testing catches UI regressions by capturing and comparing screenshots across breakpoints, validating navigation, and verifying interactions to ensure frontend quality across desktop and mobile viewports.

What is visual regression testing and when do I need it for web applications?▼

Visual regression testing detects unintended layout shifts by capturing and comparing screenshots across multiple breakpoints. It is needed for frontend release validation to ensure visual stability and interaction verification for web applications.

How do I run Playwright or Puppeteer tests for multi-phase user journeys?▼

Run Playwright or Puppeteer tests to automate multi-phase testing covering smoke, interaction, visual, and accessibility checks, validating cross-page user journeys and generating structured QA reporting.

Can I check WCAG accessibility conformance and keyboard navigation using automated browser tests?▼

Automated browser tests assess WCAG accessibility conformance by verifying keyboard navigation, focus order, and interaction flows across desktop and mobile viewports as part of the testing lifecycle.

Does browser-qa work with existing Playwright and Puppeteer dependencies?▼

Yes, browser-qa satisfies requirements for Playwright or Puppeteer integration, applying automation to frontend release validation, cross-page user journeys, and accessibility checks without requiring additional dependencies.

What is the best way to verify frontend navigation and console errors before a release?▼

The best way to verify frontend navigation and console errors is running a smoke test to check network health, validate navigation paths, and ensure interaction stability before release validation.