Automate persistent headless browser QA testing with Playwright and Chromium.
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill gstack-jia-hong-peng
Please help me install this Agent Skill. Skill: gstack Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill gstack-jia-hong-peng
Manual web application testing is slow, inconsistent, and hard to reproduce across team members. This skill eliminates browser QA friction by providing a persistent, scriptable headless browser that maintains state between commands.
Use the gstack browse skill to verify the staging deployment at https://staging.yourapp.com by navigating to the site, checking for console errors, taking a screenshot, and confirming the dashboard loads correctly.
High-intent search queries and answers about installing and using this skill.
Automate QA testing by running a long-lived headless browser daemon that maintains cookies, tabs, and login sessions across commands. This allows you to execute deterministic browser commands and turn multi-step workflows into reproducible sequences without losing state.
Yes, you can capture annotated screenshots with element labels and test responsive layouts across devices. Visual verification allows you to diff page states, inspect console and network logs, and verify that interactive elements loaded correctly.
Test a checkout flow by navigating to your staging site, snapshotting interactive elements, and filling forms using stable refs. The headless browser executes commands with sub-second latency, allowing you to verify the success state and collect screenshots for bug reports.
Yes, Playwright and the compiled browse binary are required to execute deterministic browser commands. These dependencies enable the persistent session state and sub-second latency needed for reliable site dogfooding and QA testing workflows.
Use a persistent headless browser daemon that auto-starts and maintains session state, cookies, and tabs between commands. This approach eliminates browser QA friction by keeping login sessions active across reproducible testing sequences.
robertzengcnControl a persistent headless Chromium browser for automated QA testing.
TheGoat395Run Playwright visual regression tests across desktop and mobile browsers.
uzumaki-incIdentify pages and interactable elements in a headless browser for QA workflows.
aporto-techAutomate QA testing and site dogfooding with a headless browser.
