skills.rest
GTC6244
GTC6244COMMUNITY
Explore all skills by this author →
GitHub

gstack

Run a persistent headless browser daemon for QA testing with Bun and Playwright.

Updated Apr 5, 2026
Search Tags:#automation#debugging#playwright#headless#browse#qa-testing
One-click install
npx skills add https://github.com/GTC6244/ToolBridge --skill gstack-gtc6244
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/GTC6244/ToolBridge --skill gstack-gtc6244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, persistent headless browser daemon to automate QA testing, reproduce bugs, and dogfood user flows during Claude Code sessions.

Core Features & Use Cases

  • Persistent headless browser daemon that preserves cookies and state across commands.
  • Deterministic, scriptable actions: navigate, interact, and inspect with diff and annotation support.
  • Capture bug evidence with annotated screenshots, diffs, and responsive testing across devices.
  • Use cases include validating deployments, QA regression checks, and end-to-end UI verification at scale.

Quick Start

Invoke the /browse skill to start a persistent headless browser for QA testing.

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 during Claude Code sessions?▼

You can automate QA testing by running a persistent headless browser daemon that preserves cookies and state. This enables deterministic browsing actions, diff-based verification, and annotated screenshots to validate deployments and reproduce bugs.

Do I need Playwright and Bun to run headless browser automation for bug reproduction?▼

Yes, you need both Bun and Playwright to run the local browser daemon. These dependencies provide the execution environment and browser automation capabilities required for deterministic QA testing and bug reproduction.

Can I capture annotated screenshots and diffs for UI verification across deployments?▼

Yes, you can capture bug evidence using annotated screenshots, diffs, and responsive testing across devices. This supports end-to-end UI verification and QA regression checks at scale across different deployment environments.

What is the best way to maintain browser state and cookies across multiple QA testing commands?▼

The best way to maintain state is using a persistent headless browser daemon that preserves cookies and session data across commands. This ensures deterministic, scriptable actions for reliable automation without losing context between interactions.

Does headless browser automation support responsive testing across different devices?▼

Yes, headless browser automation supports responsive testing across devices. You can capture annotated screenshots and perform diff-based verification to validate user flows and UI consistency across various screen sizes and deployment configurations.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

gstack

Automate browser QA with a persistent headless Chromium daemon.

Community
Advanced
studyzystudyzy

browse

Automate end-to-end QA browser testing with Playwright and capture screenshots.

Community
Advanced
willmiaowillmiao
1.3k

lora-manager-e2e

Automate end-to-end validation of LoRa Manager via server control and Chrome DevTools MCP.

Community
Advanced
SakshamKandelSakshamKandel

gstack

Automate QA testing with a persistent Playwright-based headless browser.

Community
Advanced