skills.rest
Jesse-L-M
Jesse-L-MCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Drive a persistent headless browser via CLI for QA testing.

Updated Mar 27, 2026
Search Tags:#automation#screenshots#qa#evidence#playwright#headless#browse
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill gstack-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill gstack-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a persistent, fast headless browser for QA testing. It enables deterministic navigation, interaction, and state verification, along with diffing, annotated screenshots, and bug evidence capture to accelerate bug reproduction and deployment validation.

Core Features & Use Cases

  • Persistent, CLI-driven headless browser for automated QA, staging validation, and bug repro.
  • Commands to navigate, interact, snapshot, diff, and annotate pages for evidence gathering.
  • Seamless integration with CLAUDE workflows and Playwright-backed browser control for reproducible testing outcomes.

Quick Start

Install gstack and start validating a site with a few browse commands to verify behavior.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I capture annotated screenshots for bug evidence during headless browser QA testing?▼

To capture annotated screenshots for bug evidence during headless browser QA testing, use a CLI-driven persistent browser that navigates pages, performs actions, and snapshots states. This approach produces reproducible outputs to accelerate bug reproduction and deployment validation.

Can I use Playwright for automated navigation and state verification in a headless browser?▼

Yes, you can use Playwright for automated navigation and state verification in a headless browser. Playwright-backed browser control enables deterministic interaction and reproducible testing outcomes when integrated with CLAUDE workflows.

What is the best way to automate staging validation without a visible browser window?▼

The best way to automate staging validation without a visible browser window is using a fast headless browser controlled by CLI commands. This enables deterministic interaction and state verification to validate site behavior and produce reproducible outputs.

How do I diff web page snapshots to verify state changes during automated testing?▼

To diff web page snapshots to verify state changes during automated testing, execute CLI commands to navigate and snapshot pages in a persistent headless browser. This allows deterministic state verification and highlights differences for bug reproduction.

Does a persistent headless browser improve reproducibility for QA testing workflows?▼

Yes, a persistent headless browser improves reproducibility for QA testing workflows by maintaining state across CLI-driven actions. This ensures deterministic navigation and reproducible outputs when validating deployments or reproducing bugs.

Related Skills

Explore More Software Engineering Skills→
dennisonbertramdennisonbertram
1

e2e-testing

Automate end-to-end browser testing with Playwright across Chromium, Firefox, and WebKit.

Community
Intermediate
proffesor-for-testingproffesor-for-testing
436

bug-reporting-excellence

Create structured bug reports with reproduction steps and environment details.

Community
Advanced
filipnyquistfilipnyquist

browse

Drive a headless browser to automate QA tasks on web apps.

Community
Advanced
stravineststravinest

QA Workflow Skill

Automate end-to-end browser QA testing with Playwright and ArangoDB checks.

Community
Advanced