skills.rest
a29paul
a29paulCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate website testing and deployment verification with persistent headless browser control.

1|Updated Apr 13, 2026
Search Tags:#automation#screenshots#playwright#browser#headless#dogfooding#qa testing
One-click install
npx skills add https://github.com/a29paul/hexlens --skill gstack-a29paul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/a29paul/hexlens --skill gstack-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of testing websites and verifying deployments by providing a persistent headless browser that navigates pages, interacts with elements, and captures visual evidence automatically.

Core Features & Use Cases

  • Persistent Browser Sessions: Auto-starts a Chromium daemon on first use (~3s), then executes commands in ~100-200ms with cookies and tabs persisting between calls.
  • Visual QA & Screenshots: Take annotated screenshots with @ref labels, test responsive layouts across viewports, and capture before/after diffs to verify changes.
  • Form & Flow Testing: Automate login flows, file uploads, and multi-step user journeys with ref-based element interaction and dialog handling.

Quick Start

Use the gstack skill to navigate to your staging URL, take a screenshot of the homepage, and verify the page loads without console errors.

Frequently Asked Questions about gstack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate website testing and capture screenshots using a headless browser?▼

Headless browser automation for website testing is handled by navigating pages, interacting with elements, and capturing annotated screenshots automatically. This Skill manages a persistent Chromium daemon to execute Playwright commands over localhost HTTP for visual QA.

Can I test responsive layouts across different viewports with Playwright?▼

Yes, responsive layout testing across viewports is supported by capturing annotated screenshots and before/after diffs. The persistent headless browser executes commands in ~100-200ms to verify layout changes across various screen sizes.

Do I need Bun runtime to run headless browser automation for QA workflows?▼

Yes, the Bun runtime is required to manage the Chromium daemon lifecycle and execute Playwright commands. The gstack browse binary works with Bun to maintain persistent browser sessions with cookies and tabs persisting between calls.

What's the best way to automate login flows and multi-step form validation without a GUI?▼

Automating login flows and form validation uses a persistent headless browser with ref-based element interaction and dialog handling. The Chromium daemon auto-starts on first use in ~3s, then executes multi-step user journeys rapidly over localhost HTTP.

Why does my headless browser test lose session cookies between page navigations?▼

Headless browser sessions maintain persistent cookies and tabs between calls by running a continuous Chromium daemon. If cookies are lost, ensure the daemon lifecycle is managed correctly via the Bun runtime rather than starting a new browser instance per command.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

gstack

Automate browser QA with a persistent headless Chromium daemon.

Community
Advanced
AndrewLi0420AndrewLi0420

gstack

Drive a headless browser with Playwright to capture diffs and screenshots.

Community
Intermediate
burgebjburgebj

browse

Automate web interactions and capture screenshots in a headless browser.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack

Automate persistent headless browser QA testing with Playwright and Chromium.

Community
Advanced