qa
Drives a headless browser through the running application, systematically exercising flows, logging defects, and fixing what it finds before re-testing.
Anatomy
| Parent repo | garrytan/gstack |
|---|---|
| Path | skills/qa |
| Trigger conditions | Slash command: /qa (report-only variant: /qa-only) |
| Instruction format | yaml-frontmatter-md |
| Required tools | shell, headless-browser |
| Reusability | stack-specific |
| Complexity | high |
| Ships scripts / examples / tests / boundaries | yes / yes / no / yes |
Failure modes
Coverage is only as good as the flow list it generates; visual defects that don't break the DOM can pass. Browser-dependency makes it the heaviest skill here to set up.
Verdict
Observation-based verification instead of self-reported success: the direction all agent QA is heading. The report-only variant is the right governance touch.
Related skills
Blocks the agent from claiming work is complete, fixed, or passing until it has run verification commands and confirmed output. Evidence…
Forces root-cause investigation before any fix: reproduce, hypothesize one cause at a time, test the hypothesis, then patch. Bans…
Frequently asked questions
What does the qa skill do?
Drives a headless browser through the running application, systematically exercising flows, logging defects, and fixing what it finds before re-testing.
When does qa trigger?
Its stated trigger: Slash command: /qa (report-only variant: /qa-only). Trigger precision is a scored reliability dimension.