gstack

Name: gstack
Availability: InStock
Author: singhianand23045

Automate QA testing and site dogfooding with a headless browser via Bash CLI and Playwright daemon.

Updated Apr 12, 2026

Search Tags:#automation #qa #diff #headless #screenshot #browse #annotation

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

gstack provides a fast headless browser workflow to automate QA testing, site dogfooding, and bug reproduction with deterministic interactions, screenshots, and diffs.

Core Features & Use Cases

Navigate pages, click elements, fill forms, and verify UI states in a repeatable manner.
Capture annotated screenshots, diffs, and diff-before/after output to simplify bug reproduction.
Test responsive layouts and generate visual evidence for deployments, CI, and bug reports.

Quick Start

Open Claude Code and run /browse to start a test session on your target site.

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 for UI states and form interactions?▼

Headless browser QA testing is automated by driving Playwright to navigate pages, click elements, fill forms, and verify UI states deterministically. It captures annotated screenshots and diffs to provide visual evidence for deployments and bug reports.

How do I capture annotated screenshots and visual diffs for bug reproduction?▼

Annotated screenshots and visual diffs are captured by running a headless browser to navigate target sites and generate diff-before/after outputs. This simplifies bug reproduction by providing deterministic visual evidence of UI state changes.

Can I use Playwright and Puppeteer for headless site dogfooding and navigation?▼

Playwright and Puppeteer are used as the underlying dependencies to drive headless site dogfooding. The workflow operates via a Bash-based CLI and a Playwright daemon to execute deterministic navigation and interaction tasks across deployments.

What is the best way to generate visual evidence for CI deployments and bug reports?▼

Visual evidence for CI deployments and bug reports is generated by automating a headless browser to test responsive layouts and capture annotated screenshots. The workflow produces diff outputs that simplify bug reproduction and verify UI states.

Do I need a Bash-based CLI to run headless browser automation and diff generation?▼

A Bash-based CLI is required to execute headless browser automation and diff generation. It communicates with a Playwright daemon to perform deterministic tasks like navigation, content reading, and screenshot capture for QA testing.

Why use headless browser diffs for testing responsive layouts across deployments?▼

Headless browser diffs are used for testing responsive layouts to detect visual regressions across deployments. By capturing diff-before/after outputs, the workflow provides deterministic, annotated visual evidence that simplifies bug reproduction.