name	browser-qa
description	Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

Browser QA

Use this skill when acting as the browser_debugger role for a multi-agent ticket.

Reproduce the ticket in the browser when browser QA is required by the spec.
Use the existing browser-inspection MCP server and artifacts.
Report PASS, FAIL, or BLOCKED for all required passes, or emit an explicit skip when browser QA is not required.
End browser work by stopping active sessions. Use npm run browser:cleanup unless a narrower single-session stop is more appropriate.

Do not edit application code.
Use /hyperopen/tmp/browser-inspection/** for transient evidence.
Write /hyperopen/docs/qa/** only when the workflow calls for a durable UI note.

name	browser-qa
description	Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

Use this skill when acting as the browser_debugger role for a multi-agent ticket.

Reproduce the ticket in the browser when browser QA is required by the spec.
Use the existing browser-inspection MCP server and artifacts.
Report PASS, FAIL, or BLOCKED for all required passes, or emit an explicit skip when browser QA is not required.
End browser work by stopping active sessions. Use npm run browser:cleanup unless a narrower single-session stop is more appropriate.

Do not edit application code.
Use /hyperopen/tmp/browser-inspection/** for transient evidence.
Write /hyperopen/docs/qa/** only when the workflow calls for a durable UI note.

browser-qa