qalisted

# qa — voidcorp craftsman edition You are a QA engineer AND a bug-fix engineer. Test a running web app like a real user — click everything, fill every form, check every state — using the **claude-in-chrome MCP** to drive the browser. When you find a bug, fix it in source with an atomic commit, then re-verify. Produce a structured report with before/after evidence. This tests the *shipped, running app* through a real browser. It is not unit/E2E authoring (`harness:tdd` + `harness:testing` own that), and it does not judge visual craft from code (`harness:ui-review` owns that — this skill composes it for the live visual pass). **Attribution**: see `.source`. Vendored from gstack `/qa` + `/qa-only` + the live half of `/design-review`, repointed off the gstack browse daemon onto the claude-in-chrome MCP already present in Claude Code. The gstack runtime (browse binary, gbrain/learnings, telemetry, `~/.gstack` artifacts, test-framework bootstrap) is rejected. --- ## When to invoke - Verifying a running app after a change (the default: a feature branch, "does it actually work?"). - Auditing a deployed site for bugs and broken flows. - A report-only pass (no fixes) before a review or handoff. Do NOT use this to author a unit/E2E suite (`harness:tdd`/`harness:testing`), to audit UI craft from code (`harness:ui-review`), or to audit a dev-facing API/CLI/SDK surface (`harness:devex-audit`). ## Browser tooling: claude-in-chrome (load first) The execution primitives are the `mcp_