gstack

Automate QA testing workflows with a Playwright-powered headless browser.

Updated Apr 1, 2026

Search Tags:#automation #testing #screenshots #qa #playwright #browser #diffs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff, and includes scripts (resource) components.

What problem does it solve?

Automates QA testing workflows by driving a headless browser to validate web pages and capture reproducible evidence.

Core Features & Use Cases

Navigate pages, interact with UI elements, and inspect state across sessions.
Diff changes before and after actions and generate annotated screenshots for bug reproduction.
Test responsive layouts, forms, uploads, and dialogs, and capture concrete evidence for issues.

Quick Start

Tell me the site you want to test and the interactions to perform, and I will run the test and return the results with evidence.

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 and capture screenshots for bug reproduction?▼

Automate QA testing by driving a headless browser to validate web pages, interact with UI elements, and capture annotated screenshots as concrete evidence for bug reproduction.

Can I use Playwright to test responsive layouts and perform regression checks?▼

Playwright drives a headless browser to test responsive layouts, forms, uploads, and dialogs, enabling regression checks across deployments by diffing changes before and after actions.

How do I generate diffs of web pages before and after interactions?▼

Generate diffs of web pages by navigating pages, interacting with UI elements, and inspecting state across sessions to capture reproducible evidence of changes.

Do I need a headless browser to validate dynamic content across cross-page flows?▼

A headless browser is required to validate dynamic content across cross-page flows, performing navigation, interaction, state inspection, and diffing automatically.

What is the best way to test forms, uploads, and dialogs automatically?▼

The best way to test forms, uploads, and dialogs automatically is using a Playwright-powered daemon to drive interactions and capture annotated screenshots of issues.

How do I inspect state across sessions during browser automation?▼

Inspect state across sessions during browser automation by navigating pages, interacting with UI elements, and diffing changes to validate web pages and capture reproducible evidence.