gstack

Automate QA tasks with a headless browser via Bun and Playwright.

Updated Mar 11, 2026

Search Tags:#automation #qa #diff #playwright #headless #screenshot #gstack

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, playwright.

What problem does it solve?

gstack automates end-to-end QA testing by driving a headless browser to navigate pages, interact with UI, and verify states, reducing manual debugging time and providing repeatable tests.

Core Features & Use Cases

Navigate URLs, click elements, fill forms, read page content, and verify results from the CLI.
Take annotated screenshots and generate diffs to confirm actions had the intended effect.
Diff baselines vs current state to validate changes and support bug reproduction.
Isolate workspaces per project to avoid cross-project interference.
Capture console, network, and dialog events for comprehensive debugging.

Quick Start

Run the compiled gstack binary and issue commands like goto, text, and screenshot to validate a page.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate headless QA testing for UI regression checks?▼

Headless QA testing automates UI regression checks by driving a browser to navigate pages, interact with elements, and verify page states. gstack executes these tasks via a compiled binary to provide repeatable end-to-end test coverage.

Do I need Bun and Playwright installed locally to run headless browser tests?▼

Yes, you need Bun and Playwright installed locally to run headless browser tests. The workflow requires these dependencies to execute the compiled binary, drive the browser automation, and generate per-workspace logs and diffs.

How can I take annotated screenshots and generate diffs for feature verification?▼

To take annotated screenshots and generate diffs for feature verification, you issue screenshot commands via the CLI. The headless browser captures the current page state and compares it against baseline images to validate changes.

Can I capture console and network events during automated UI interactions?▼

Yes, you can capture console, network, and dialog events during automated UI interactions. gstack intercepts these browser events to provide comprehensive debugging data alongside the standard page navigation and form filling operations.

What is the best way to isolate QA test workspaces across different projects?▼

Isolating QA test workspaces across different projects prevents cross-project interference during test execution. gstack natively isolates workspaces per project, ensuring logs, diffs, and baselines remain cleanly separated for reliable regression checks.