Skip to content
OpenPlanr Docs
GitHub (opens in a new tab)

Skill · Review and QA

/browser-qa

Exercise the running app in a real browser, from routes and forms to phone sizes, accessibility, the console, and the network. It reports what it found and leaves the fixes to you.

Run it
/browser-qa

in Claude Code. If /browser-qa runs another command, use /planr:browser-qa.

What it does

Run practical browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior. Use for UI, authentication, session, navigation, or browser-network changes.

Browser QA infers the routes, journeys, and sizes from your request and the repository, then starts or reuses the project's local runtime. It checks navigation, forms, responsive layout, keyboard access, visible focus, accessible names, console errors, failed requests, and the loading and error states the change touches. It never stores credentials, cookies, or session secrets.

The reply gives the outcome (pass, issues found, or blocked), the coverage it exercised, and reproducible findings with the page and the expected behavior. A check it could not run is reported as unverified, never as a pass. See Review before it lands.

When to use it

Use it to

  • Test this page or application in a real browser
  • Check routes, forms, mobile viewports, accessibility, console, and network behavior

Not for

  • Run backend unit tests only
  • Review a plan without exercising a browser

Example

/browser-qa the sign-in flow on /login at phone and desktop sizes, including the expired-link error

Prompts and commands

Next in the loop

/land

Check whether reviewed work is ready to merge, publish, or deploy, and get the landing sequence in order. Land prepares the steps and never runs them.

OpenPlanr Docs
Commands for
Theme