Automate browser-driven QA testing with a persistent headless browser.
npx skills add https://github.com/ekrishgupta/gemstack --skill gemstack
Please help me install this Agent Skill. Skill: gemstack Source: https://github.com/ekrishgupta/gemstack/tree/main Command: npx skills add https://github.com/ekrishgupta/gemstack --skill gemstack
Gemstack provides a fast, persistent headless browser and a workflow of skills to streamline QA testing, product dogfooding, and release readiness. It eliminates the friction of setting up and maintaining a browser-driven QA loop across local development and staging URLs.
To start, run the gemstack CLI and invoke /office-hours to frame your problem.
High-intent search queries and answers about installing and using this skill.
Headless browser QA testing is automated by using a persistent Playwright-backed daemon to execute navigation, text extraction, click, fill, and form interactions. This enables repeatable automated browser-driven QA across local development and staging environments with sub-second command latency.
Yes, you can capture annotated screenshots and perform diffed verification during e2e testing. The workflow allows you to compare before and after states directly, producing visual evidence for bug reports and release readiness.
A persistent headless browser maintains a continuous browser daemon instead of launching new instances per test. This architecture provides sub-second command latency for QA automation and includes automatic idle shutdown to conserve resources.
Yes, Playwright and diff are required dependencies to run browser-driven QA workflows. The Skill relies on a Bun-based binary powered by Playwright to manage the persistent browser daemon and perform diffed verification of content states.
The best way to start planning product dogfooding and design reviews is to invoke the /office-hours command. This frames your problem and aligns product decisions with real usage through structured design consultation and review workflows.
Limitations of headless browser automation include reliance on a persistent daemon that requires active management, though it features automatic idle shutdown. It is specifically designed for local development, staging, and QA pipelines rather than large-scale production scraping.
imonmiAutomate browser QA with a persistent headless Chromium daemon.
emmepraIdentify and validate verification checks for code changes and CI readiness.
cnoe-ioAggregate GitHub, ArgoCD, and Jira data into a Go/No-Go release verdict.
GTC6244Run a persistent headless browser daemon for QA testing with Bun and Playwright.
