browser-qa

Automate visual and interaction testing for web user interfaces.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill browser-qa-maelwalser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/browser-qa
Command: npx skills add https://github.com/Maelwalser/claude-config --skill browser-qa-maelwalser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, automated way to verify that deployed web features render correctly, user interactions work end-to-end, and regressions or accessibility issues are detected before release.

Core Features & Use Cases

  • Smoke Testing: Navigate pages, detect console errors, and ensure no 4xx/5xx network failures.
  • Interaction Verification: Exercise navigation, forms, auth flows, and critical user journeys to validate success and error states.
  • Visual Regression & Accessibility: Capture screenshots across breakpoints for diffing against baselines and run axe-core scans for WCAG AA checks.
  • Use Case: Run after a staging deployment or during PR review to confirm UI stability, Core Web Vitals, and accessibility compliance.

Quick Start

Run a full browser QA pass against the staging URL and produce a consolidated QA report.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I automate visual UI testing for staging and preview deployments?

Automate visual UI testing by navigating pages, capturing screenshots across breakpoints, and diffing them against baselines to detect regressions on staging and preview deployments before release.

Can I run axe-core accessibility scans for WCAG AA compliance during pull request reviews?

Yes, you can run axe-core accessibility scans to check for WCAG AA compliance during pull request reviews, validating that new code changes do not introduce accessibility issues before merging.

Does automated browser QA work with Playwright and Puppeteer?

Automated browser QA works with Playwright and Puppeteer, requiring a browser automation controller to exercise navigation, forms, and authentication flows while checking for console and network errors.

What is the best way to check Core Web Vitals and detect 4xx or 5xx network failures post-deploy?

Run a post-deploy smoke testing pass to validate Core Web Vitals thresholds and monitor network requests, ensuring deployed web features render correctly without any 4xx or 5xx network failures.

How do I verify user interactions like forms and authentication flows end-to-end?

Verify user interactions by exercising navigation, forms, and authentication flows end-to-end to validate both success and error states, ensuring critical user journeys work correctly before release.