browser-qa
browser qa
What it does
- 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
- Console errors: 0 critical, 2 warnings (analytics noise)
- Network: all 200/304, no failures
Requirements & configuration
- When you need to verify UI behavior across pages
- mass-update) against a production URL — require an explicit opt-in and a staging/preview
- not sufficient — keyboard nav, focus order, and a screen-reader pass still need a manual
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
browser-qa FAQ
What does the browser-qa skill do?
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features. After deploying a feature to staging/preview When you need to verify UI behavior across pages
What does browser-qa require?
When you need to verify UI behavior across pages mass-update) against a production URL — require an explicit opt-in and a staging/preview not sufficient — keyboard nav, focus order, and a screen-reader pass still need a manual
How do I install browser-qa?
Run: npx -y skills add https://github.com/affaan-m/everything-claude-code --skill browser-qa --agent claude-code — the source lives at github.com/affaan-m/everything-claude-code.
Maintain browser-qa?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[browser-qa on getagentictools](https://getagentictools.com/skills/affaan-m-everything-claude-code-browser-qa?ref=badge) npx agentictools info skills/affaan-m-everything-claude-code-browser-qa The second line is the CLI lookup for this page — handy in READMEs and docs.
