gstack

Name: gstack
Availability: InStock
Author: stayconnectquick

Automate QA testing with a persistent headless Chromium browser via Playwright.

Updated May 6, 2026

Search Tags:#automation #testing #qa #playwright #browser #ref-snapshot

Ready to run

npx skills add https://github.com/stayconnectquick/gstack --skill gstack-stayconnectquick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/stayconnectquick/gstack/tree/main
Command: npx skills add https://github.com/stayconnectquick/gstack --skill gstack-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, puppeteer-core, marked, @huggingface/transformers, @ngrok/ngrok, and includes scripts (resource) components.

What problem does it solve?

The gstack Skill unit provides a complete, fast headless browser workflow that enables QA testing, site dogfooding, and automated checks against live pages using a persistent Chromium daemon and Playwright commands.

Core Features & Use Cases

Deterministic page navigation, element interaction, and snapshotting with ref-based selectors.
Real-browser mode with headed window, side panel, pair-agent support, and safety rails.
Use cases include regression testing, visual QA, performance checks, and dev-experiences QA.

Quick Start

Goto a URL, snapshot the page for refs, and run a basic QA flow.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate QA testing with Playwright against live staging pages?▼

Automate QA testing by driving a persistent headless browser to execute deterministic Playwright commands against live pages. It records page state using ref-based snapshotting, enabling repeatable regression checks and visual diffs for staging deployments.

What is ref-based snapshotting for browser automation and how does it work?▼

Ref-based snapshotting captures page state by assigning deterministic reference selectors to elements during browser automation. This mechanism allows reliable element interaction and visual diffs for repeatable QA checks across different deployments.

Can I run regression testing in a real-browser mode instead of a headless environment?▼

Yes, you can run regression testing in real-browser mode using a headed window. This mode supports pair-agent workflows and includes safety rails while maintaining the same deterministic page navigation and snapshotting capabilities.

Does gstack require a persistent Chromium daemon for site dogfooding workflows?▼

Site dogfooding workflows require a persistent Chromium daemon to maintain browser state during automation. This persistent headless environment enables continuous page navigation, element interaction, and automated test feeds across live deployments.

What is the best way to perform visual QA checks on deployments without manual testing?▼

Perform visual QA checks by automating deterministic browser commands via Playwright to navigate live pages and capture snapshots. This approach generates visual diffs and repeatable checks, replacing manual testing with an isolated execution pipeline.

Why are my automated browser commands failing during visual diffs on live pages?▼

Automated browser commands during visual diffs may fail if strict token scopes are violated or the execution pipeline is compromised. The isolated environment enforces safety rails, requiring deterministic ref-based selectors for reliable page state recording.