browser-qa

Automate end-to-end browser QA for web applications with smoke, interaction, visual regression, and accessibility checks.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/samymity/node-poc --skill browser-qa-samymity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/samymity/node-poc/tree/main/.claude/skills/browser-qa
Command: npx skills add https://github.com/samymity/node-poc --skill browser-qa-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual browser quality assurance is slow, inconsistent, and easy to miss critical UI issues across different viewports and user flows. This Skill automates end-to-end browser testing to catch layout bugs, broken interactions, and accessibility violations before they impact users.

Core Features & Use Cases

  • Smoke Testing: Automatically checks for console errors, failed network requests, and Core Web Vitals compliance on deployed pages.
  • Interaction Validation: Tests navigation links, form submissions (valid and invalid inputs), authentication flows, and critical user journeys like checkout or onboarding.
  • Visual Regression Testing: Captures screenshots across mobile, tablet, and desktop breakpoints to flag layout shifts, overflow, missing elements, and dark mode inconsistencies.
  • Accessibility Auditing: Runs automated WCAG AA checks, verifies keyboard navigation, and validates screen reader landmark support. Ideal for frontend teams running QA after staging deployments, reviewing PRs with UI changes, or performing pre-ship validation to avoid broken user experiences.

Quick Start

Use the browser-qa skill to run a full quality check on your staging deployment URL immediately after pushing new frontend code.

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 smoke testing to catch console errors and failed network requests?

Automated browser smoke testing checks deployed staging pages for console errors, failed network requests, and Core Web Vitals compliance. It automatically validates page health immediately after pushing new frontend code to catch UI bugs pre-ship.

What is the best way to run visual regression testing across mobile and desktop breakpoints?

Visual regression testing captures screenshots across mobile, tablet, and desktop breakpoints to flag layout shifts, overflow, missing elements, and dark mode inconsistencies. This automated cross-breakpoint validation catches UI layout bugs before they impact users.

How do I automate accessibility auditing for WCAG AA compliance and keyboard navigation?

Automated accessibility auditing runs WCAG AA checks, verifies keyboard navigation, and validates screen reader landmark support. This ensures frontend applications meet compliance standards and catch accessibility violations during pre-deploy validation.

Can I automate frontend interaction validation for form submissions and authentication flows?

Interaction validation tests navigation links, form submissions with valid and invalid inputs, authentication flows, and critical user journeys like checkout or onboarding. This automated validation ensures broken interactions are caught during staging environment testing.

Does automated UI validation work for reviewing pull requests with frontend changes?

Automated UI validation is ideal for reviewing PRs with frontend changes. It coordinates smoke testing, interaction validation, visual regression, and accessibility checks to catch layout bugs and broken interactions before merging code.