browser-qa

Automates visual testing and UI interaction verification on deployed web pages via browser automation.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill browser-qa-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/browser-qa
Command: npx skills add https://github.com/ibytechaos/claude --skill browser-qa-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying that a deployed feature actually works across pages, viewports, and user flows is slow and error-prone. This Skill automates post-deployment QA by driving a real browser to catch console errors, broken links, layout regressions, and accessibility violations before users do. ## Core Features & Use Cases - Smoke Testing: Navigates to target URLs, checks console errors, network failures, and Core Web Vitals (LCP, CLS, INP) on desktop and mobile viewports. - Interaction & Visual Regression Testing: Clicks nav links, submits valid and invalid form data, tests auth flows, and screenshots pages at 375px, 768px, and 1440px breakpoints to flag layout shifts. - Accessibility Audits: Runs axe-core checks for WCAG AA violations, keyboard navigation, and screen reader landmarks. - Use Case: After deploying a new checkout flow to staging, run this Skill to verify the full purchase journey, confirm forms show proper error states, and produce a structured QA report with a ship/no-ship verdict. ## Quick Start Run a browser QA pass on https://staging.example.com and report any console errors, broken interactions, visual regressions, and accessibility issues.

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 testing after deploying a feature?

Use browser automation to navigate to the deployed URL, capture screenshots at multiple breakpoints (375px, 768px, 1440px), and compare them against baselines. Flag layout shifts over 5px, missing elements, and overflow issues in a structured report.

What browser automation tools work for UI testing with Claude?

This workflow supports claude-in-chrome MCP tools (using your actual Chrome), Playwright via browserbase MCP, or direct Puppeteer scripts. Any of these can drive page navigation, form submission, and screenshot capture.

How to check Core Web Vitals during QA testing?

Measure LCP, CLS, and INP on the target page during the smoke test phase. Passing thresholds are LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds.

Can browser automation test accessibility compliance?

Yes, run axe-core or an equivalent engine on each page to detect WCAG AA violations such as contrast failures, missing labels, and focus order problems. Also verify keyboard navigation and screen reader landmarks end to end.

When should I run automated browser QA versus unit tests?

Run browser QA after deploying to staging or preview environments, when reviewing frontend PRs, and before shipping. Unit tests cover logic in isolation, while browser QA verifies real rendered behavior, network requests, and user journeys.