gstack

Orchestrate headless Chromium to automate end-to-end web QA via CLI.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/psyche911/investor-council-app --skill gstack-psyche911
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/psyche911/investor-council-app/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/psyche911/investor-council-app --skill gstack-psyche911

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, playwright, diff.

What problem does it solve?

Automates browser-based QA and dogfooding workflows so you can verify web app behavior quickly and with evidence.

Core Features & Use Cases

  • Persistent headless Chromium with a CLI interface for navigating pages, interacting with elements, and validating state.
  • Snapshotting, diffing, and annotated screenshots to capture evidence for bugs and deployments.
  • Multi-page/testing workflows: login, form submissions, file uploads, responsive layouts, and regression checks.

Quick Start

Run a test flow by navigating to a URL with the browse CLI and capture an annotated diff-ready report.

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 for web applications?

Headless browser QA is automated by orchestrating a local headless Chromium server to execute end-to-end test flows, navigate pages, and interact with elements. This approach enables rapid validation and repeatable testing for deployments.

Can I capture screenshots and diff results during Playwright test flows?

Yes, you can capture annotated screenshots and snapshot page states to generate diffed results during Playwright test flows. This evidence capture mechanism validates bugs and verifies deployment behavior deterministically.

What do I need to run end-to-end browser automation locally?

You need bun, playwright, and diff installed to run end-to-end browser automation locally. These dependencies support persistent headless Chromium control, CLI navigation, and output diffing for validating web app behavior.

What's the best way to validate responsive layouts and form submissions in headless browser testing?

The best way to validate responsive layouts and form submissions is by running multi-page testing workflows through a headless browser CLI. These workflows handle login sequences, file uploads, and regression checks to verify web app state.

Why use a local headless browser server for deployment dogfooding instead of manual checks?

A local headless browser server automates deployment dogfooding workflows to verify web app behavior quickly and with evidence. It satisfies requirements for deterministic browser control, diffed results, and accessible outputs via a CLI.

Does gstack support regression checks for multi-page testing workflows?

Yes, gstack supports regression checks through multi-page testing workflows that handle login, form submissions, file uploads, and responsive layouts. It captures snapshot diffs and annotated screenshots to validate state across test flows.