gstack

Automates browser QA by driving a persistent Chromium daemon via Bun and Playwright CLI commands.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill gstack-liambiswell20-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Liambiswell20-tech/Bolus-Brain/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill gstack-liambiswell20-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based QA by driving a persistent Chromium daemon to perform real interactions, verify outcomes, and collect evidence across repeat runs.

Core Features & Use Cases

  • Persistent browser sessions with cookies, localStorage, and open tabs to enable deterministic replays.
  • Rich command surface for navigation, content extraction, interaction, and inspection, including snapshot diffs and annotated screenshots.
  • Use cases include regression testing, deployment verified QA, and bug reproduction with auditable evidence.

Quick Start

Verify behavior and capture evidence with a single, straightforward command.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate browser-based QA testing with Playwright?

Automate browser-based QA by driving a persistent Chromium daemon to execute real interactions, verify outcomes, and collect evidence across repeat runs using a compact CLI.

Can I maintain persistent browser sessions for deterministic regression testing?

Persistent browser sessions retain cookies, localStorage, and open tabs, enabling deterministic replays for regression testing, deployment verification, and bug reproduction.

How do I capture annotated screenshots as evidence during bug reproduction?

Capture annotated screenshots and snapshot diffs during bug reproduction by utilizing the skill's rich command surface for navigation, interaction, and page inspection.

Do I need bun and Playwright to run headless QA tests?

Yes, you need bun and Playwright installed, as the skill requires both to drive the persistent Chromium daemon and expose its compact CLI for headless QA testing.

What is the best way to verify web application deployments through browser automation?

Verify web application deployments by driving a persistent Chromium daemon to execute real interactions and verify outcomes, providing an auditable testing workflow with collected evidence.

Are there limitations when using a headless browser daemon for regression checks?

The headless browser daemon approach is limited to environments supporting bun and Playwright, focusing on deterministic, auditable workflows rather than visual exploratory testing.