Browser Qa

Automates the QA grind after you ship to staging: drives a real browser through smoke tests, interaction flows, visual regression checks, and accessibility audits. It'll catch console errors, dead links, broken forms, layout shifts across three breakpoints, and WCAG violations before they hit production. The safety model is smart: defaults to read-only journeys and won't let you accidentally run a checkout flow against prod without explicit opt-in. Outputs a structured verdict (SHIP / SHIP WITH FIXES / DO NOT SHIP) with screenshots and Core Web Vitals. Works with any browser MCP. Honestly, this is the kind of thing you write yourself in bits and pieces over six months, so having it packaged saves you from maintaining yet another Playwright script.

skills.sh installs: 6K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --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