qa-only (gstack)
- QA
Runs a thorough QA pass over a web app and REPORTS every defect it finds without changing any code, leaving the fixes to the team. It is the report-only variant — distinct from a sweep that also repairs the bugs, from merely driving a headless browser to look at the site, and from measuring performance.
A situation it fits
Test my site and give me a list of everything that is wrong. Do not fix anything; I want to review the findings first.
3 scenarios in the bank answer to qa-only (gstack). The rest are in the game.
Skills it gets confused with
These share a family with qa-only (gstack), which is another way of saying they are the ones you might reach for by mistake.
- benchmark (gstack)Detects performance regressions by measuring how fast pages and interactions run and comparing them against a baseline, so a change that made things slower is caught. It is about speed over time, not finding functional bugs, reporting them, or driving the browser to look at the page.
- browse (gstack)A fast headless browser for opening a running site, clicking through flows, and seeing what actually renders — a tool for dogfooding and eyeballing the app, not a systematic bug hunt. It drives and views the site rather than producing a QA report, fixing defects, or benchmarking speed.
- qa (gstack)Systematically tests a running web app for bugs AND fixes each one it finds in the same pass, so you end up with a working product rather than a defect list. The fixing is the point — unlike a report-only QA sweep, a plain headless browser for eyeballing the site, or a performance-regression check.
Knowing what qa-only (gstack) does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessionqa-only (gstack) is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.