Browser Qa

Automates the QA checklist you'd normally run manually before shipping frontend changes. After deploying to staging, it navigates your site like a real user, checks console errors and network failures, screenshots three breakpoints, tests forms and auth flows, runs accessibility audits, and spits out a pass/fail report with Core Web Vitals. Works with claude-in-chrome, Playwright, or Puppeteer. The four-phase approach (smoke test, interactions, visual regression, accessibility) catches the obvious stuff that slips through: overflowing containers on mobile, missing form validation, broken nav links. Honestly most useful when you're touching UI code you didn't write and need confidence it still works.

skills.sh installs: 4.3K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill browser-qa --agent claude-code

Installs into .claude/skills of the current project.

Files

Browser QA — Automated Visual Testing & Interaction

When to Use

After deploying a feature to staging/preview
When you need to verify UI behavior across pages
Before shipping — confirm layouts, forms, interactions actually work
When reviewing PRs that touch frontend code
Accessibility audits and responsive testing

How It Works

Uses the browser automation MCP (claude-in-chrome, Playwright, or Puppeteer) to interact with live pages like a real user.

Safety first — blast radius (run read-only by default)

Browser QA drives real auth and real user journeys, so treat the blast radius explicitly. Default to read-only: never run a mutating journey (checkout, payment, delete, mass-update) against a production URL — require an explicit opt-in and a staging/preview URL. Use seeded test credentials, never real production logins, and redact credentials/tokens/PII before saving any screenshot.

SKILL.md on GitHub