gstack

Automate browser-based QA tasks with Playwright and capture reproducible evidence.

Updated Aug 27, 2026

Search Tags:#automation #testing #debugging #qa #playwright #browser

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate pages, interact with UI, verify state, and capture bug evidence using a fast headless browser for QA testing and dogfooding.

Core Features & Use Cases

Automated QA flows: drive a headless browser to navigate, click, fill, and verify UI states across deployments.
Evidence capture: diff before/after changes, take annotated screenshots, and collect bug repro data.
Responsive testing: verify layouts across breakpoints and generate visuals for PRs.

Quick Start

Use gstack to run a basic QA session on a local site, capture evidence, and file a bug report with screenshots.

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 with a headless browser?▼

Headless browser QA testing automates page navigation, UI interaction, and state verification using Playwright to drive the browser and capture evidence. You can navigate, click, fill forms, and verify deployments reproducibly without a graphical interface.

What's the best way to capture bug evidence during site testing?▼

Capturing bug evidence during site testing involves running automated QA flows to diff before and after changes, take annotated screenshots, and collect bug reproduction data. This ensures you have consistent visual proof and reproducible steps for deployment verification.

Can I use Playwright to verify responsive layouts across breakpoints?▼

Yes, you can use Playwright to verify responsive layouts across breakpoints by driving a headless browser to capture visuals and generate responsive testing evidence. This allows you to confirm UI state and layout consistency across different screen sizes for PRs.

Does headless QA testing work for local site dogfooding?▼

Headless QA testing works for local site dogfooding by driving a browser to navigate pages and interact with UI elements. It captures reproducible steps and evidence, ensuring consistent test results across local and deployment environments.

How do I generate visuals for PRs using browser automation?▼

Generating visuals for PRs uses browser automation to verify layouts across breakpoints and capture annotated screenshots. By driving a headless browser through QA flows, you produce consistent visual evidence that tracks UI state changes before and after deployments.