gstack

Automate browser-based QA tasks with a persistent Playwright daemon.

Updated Mar 14, 2026

Search Tags:#automation #observability #diff #playwright #browser #screenshot #qa-testing

Ready to run

npx skills add https://github.com/Bradliebs/VolumeTurtle --skill gstack-bradliebs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It provides a fast, persistent headless browser for QA testing and site dogfooding, replacing tedious manual browsing with automated exploration, interaction, and evidence collection.

Core Features & Use Cases

Automated navigation and interaction: visit pages, click elements, fill forms, upload files, and test flows.
Diffs and annotated evidence: diff before/after states and generate annotated screenshots for PRs and bug reports.
Responsive testing: verify layouts across multiple viewports and devices.
Observability and audits: emit structured logs and per-project state to enable traceability and regression detection.

Quick Start

Boot gstack and run a browse command against your site to start collecting QA evidence in context.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate browser QA testing with Playwright inside Claude Code?▼

Automate browser QA testing by booting a persistent Playwright daemon that navigates pages, clicks elements, fills forms, and generates annotated screenshots. It provides per-project state and structured logs for observability and regression detection.

Can I generate annotated screenshots and diff before/after states for bug reports?▼

Generate annotated screenshots and diff before/after states to provide visual evidence for PRs and bug reports. The tool captures page interactions and layout changes across multiple viewports for responsive testing and regression detection.

What is the best way to verify deployments and reproduce bugs using a headless browser?▼

Verify deployments and reproduce bugs by running automated browser workflows against your site. The persistent headless browser applies structured logs and per-project state to enable traceability and collect regression evidence without manual browsing.

Does gstack support responsive testing across multiple viewports and devices?▼

Responsive testing across multiple viewports and devices is supported by the automated browser workflows. You can verify layouts by navigating pages and capturing annotated visual evidence across different screen sizes using the Playwright daemon.

How do I collect structured logs and per-project state for regression detection?▼

Collect structured logs and per-project state for regression detection by running automated browser workflows. The tool emits observability data during navigation and interaction, enabling traceability and audits across your QA testing sessions.