skills.rest
concept2cure
concept2cureCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate browser-based QA with a persistent headless browsing daemon.

1|Updated Nov 13, 2025
Search Tags:#qa#diff#playwright#browser#headless#snapshot
One-click install
npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill gstack-concept2cure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill gstack-concept2cure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, persistent headless browser workflow for QA testing and site dogfooding, enabling Claude Code to interact with real pages reliably and capture evidence.

Core Features & Use Cases

  • Persistent browser daemon: start once, reuse across commands for speed and state retention.
  • Snapshotting & refs: assign @e refs to accessibility nodes for reliable element interactions.
  • Annotated evidence: diff, annotated screenshots, and baseline comparisons to verify changes.
  • QA workflows: forms, uploads, dialogs, cookies, responsive checks, and production-like test captures.

Quick Start

Invoke /browse to start the persistent headless browser and begin QA sessions.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate headless browser QA testing with persistent state?▼

Automate headless browser QA by starting a persistent daemon that retains state across commands. This allows reliable element interaction using snapshot refs and cross-command state persistence for continuous testing workflows.

What is diff-based verification for browser snapshot testing?▼

Diff-based verification compares current browser snapshots against baseline captures to verify UI changes. It generates annotated screenshots highlighting visual differences, driving targeted debugging and thorough QA reviews.

How do I interact with accessibility nodes for reliable browser automation?▼

Interact with accessibility nodes by assigning @e refs to specific elements within a browser snapshot. This ref system ensures stable, reliable element targeting during automated headless QA workflows and form interactions.

Can I run headless browser snapshots locally without external dependencies?▼

Yes, headless browser snapshots run securely in a local execution environment with bounded resources. The browser manager enforces these constraints while maintaining a stable API surface via the CLI.

What's the best way to capture annotated evidence during Playwright QA workflows?▼

Capture annotated evidence by utilizing the snapshot and ref system to generate diff comparisons and baseline screenshots. This produces visual evidence of page states, dialogs, and responsive checks for QA reviews.

Why does my browser QA workflow lose state between separate commands?▼

Browser QA workflows lose state without a persistent daemon running. Starting a persistent headless browser daemon resolves this by retaining cross-command state, enabling continuous task execution without session resets.

Related Skills

Explore More Software Engineering Skills→
mi179mi179
1

gstack

Launch a Playwright-backed headless browser for QA testing and live-site verification.

Community
Advanced
studyzystudyzy

qa-only

Generate structured QA reports with health scores, screenshots, and repro steps.

Community
Advanced
BuilderIOBuilderIO
11

playwright-cli

Automate browser interactions and Playwright test workflows via command-driven tooling.

Official
Advanced
TimHL5TimHL5

gstack

Drive a persistent headless Chromium daemon via CLI for browser automation.

Community
Advanced