browser-qa

Automate end-to-end web app testing in Chrome with auto-discovered screens.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end web app testing is often manual, brittle, and time-consuming. This Skill automates discovery of screens and interactive elements, validates functionality, logs issues, and launches inline fix agents within a Chrome-based workflow.

Core Features & Use Cases

  • Auto-discovers screens and interactive elements from the DOM without project-specific setup.
  • Spawns fix agents inline to reproduce and validate bugs, then re-tests automatically.
  • Supports targeted workflow testing and structured bug-fix cycles for robust QA.

Quick Start

Run /browser-qa with a URL to begin automated testing across the app.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I automate end-to-end web testing in Chrome without writing manual test scripts?

End-to-end web testing in Chrome can be automated by auto-discovering screens and interactive elements directly from the DOM. This approach validates navigation, form handling, and workflows without requiring project-specific setup or manual scripting.

Can I automatically fix bugs discovered during e2e testing?

Yes, e2e testing workflows can automatically spawn inline fix agents to reproduce and validate bugs. Once a bug is remediated, the system re-tests automatically to confirm the fix within the structured bug-fix cycle.

Do I need the Chrome extension to run automated web app testing?

Yes, automated web app testing requires the Claude in Chrome extension to be connected. This extension facilitates the browser-based workflow needed to discover screens, validate interactions, and launch inline fix agents.

What is the best way to test specific web application workflows rather than the entire app?

Targeted workflow testing is supported using the --workflow mode. This allows you to guide the automated testing process toward specific user journeys or sequences within the web application instead of scanning the entire app.

Does automated QA testing support accessibility and performance checks?

Yes, automated QA testing supports accessibility and performance checks as part of its end-to-end validation. It evaluates web application interactions across discovered screens to ensure compliance and optimal performance.

When should I use the --fix mode for bug-fix cycles?

The --fix mode should be used when you need to guide automated bug remediation during testing. It enables the system to launch inline fix agents that reproduce issues, apply fixes, and automatically re-test the affected workflows.