Skill

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.

Situations it fits

Spin up a headless browser so I can load a page and check what it actually shows right now.

Browse. All four touch a running web app, which is the trap. browse just drives a headless browser to open the site and see what renders - a tool for eyeballing, not a bug sweep. By contrast qa systematically tests the app AND fixes each bug it finds, so you end up with a working product; qa-only tests the app and REPORTS the defects without changing any code, leaving fixes to the team; benchmark measures speed and flags performance regressions against a baseline, not functional bugs.

You just want to quickly open your running site in a headless browser, click through a couple of flows, and see what actually renders - a fast way to eyeball the app, not a formal bug hunt.

3 scenarios in the bank answer to Browse. The rest are in the game.

Skills it gets confused with

These share a family with Browse, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Browse does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Browse is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.