| name | qa |
| description | Structured QA workflow for Codex using Browser, Chrome, Computer Use, or repo-local tests. Use for site QA, feature-branch testing, or evidence-backed quality reports. |
QA
Use this skill for systematic QA on a web application or feature branch.
This port is adapted from garrytan/gstack at commit 2aa745cb0e4331d683e727ec77385d04cdbb45a2.
Modes
diff-aware: default when on a feature branch and no explicit URL is givenfull: broad exploratory QA on a target URL or appquick: smoke testregression: compare against a prior baseline or report
Workflow
- Choose a browser/runtime path using the
browse skill guidance, including @Browser, @Chrome, Computer Use, or repo-local test tooling as appropriate.
- Identify the target URL or feature-branch scope.
- Use
references/issue-taxonomy.md while exploring.
- Write results into the structure from
templates/qa-report-template.md.
- End with a health score, top issues, and any blockers or blind spots.
Branch-Aware Behavior
If the user asks for QA on a feature branch with no URL:
- inspect the diff against
origin/main
- infer the pages or routes likely affected
- test the changed surface first
- check adjacent pages for regressions
Guardrails
- Be explicit when runtime/tooling limits prevented full coverage.
- Document issues as you find them instead of batching vague notes.
- Prefer reproducible evidence over general impressions.
