skills.rest
mattothomas
mattothomasCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Drive a headless Chromium daemon to automate browser-based QA tasks.

Updated Mar 28, 2026
Search Tags:#qa#diff#playwright#headless#screenshot#browse
One-click install
npx skills add https://github.com/mattothomas/sp26_hackpsu --skill gstack-mattothomas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/mattothomas/sp26_hackpsu/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/mattothomas/sp26_hackpsu --skill gstack-mattothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Enable rapid, repeatable QA testing by driving a persistent headless browser that captures interactions, state, and evidence.

Core Features & Use Cases

  • Persistent state with cookies and sessions for reliable testing across steps
  • Snapshot, diff, and annotated screenshots to reproduce bugs visually
  • Supports form filling, navigation, and accessibility checks for real-world QA

Quick Start

Start a test session by invoking the browse CLI to interact with a test site and get instant bug evidence.

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 testing with persistent sessions?▼

Headless browser QA testing uses a persistent Chromium daemon to maintain cookies and sessions across steps. This enables reliable, repeatable site testing without losing state between interactions.

How do I capture visual diffs and annotated screenshots to reproduce bugs?▼

Visual diffs and annotated screenshots are captured by driving a headless browser sandbox to snapshot interactions and state. This produces reproducible visual evidence for bug reproduction and design reviews.

Do I need Playwright and a Bun CLI to run headless browser testing?▼

Yes, Playwright and a Bun-based CLI are required to run commands, manage persistent state, and produce annotated evidence for headless browser testing.

Can I perform form filling and accessibility checks in a reproducible sandbox?▼

Form filling, navigation, and accessibility checks are supported within a reproducible headless browser sandbox. This allows real-world QA testing of site interactions and compliance.

What's the best way to manage cookies for repeatable site testing?▼

Cookie management is handled by driving a persistent headless browser daemon that retains sessions across steps. This ensures repeatable site testing without manual authentication overhead.

Related Skills

Explore More Software Engineering Skills→
Chang-Shih-YungChang-Shih-Yung

gstack

Run a persistent headless Chromium daemon with Playwright under Bun via HTTP.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
Menschlichkeit-OsterreichMenschlichkeit-Osterreich

browser-use

Automate browser interactions for web testing, form filling, screenshots, and data extraction.

Official
Advanced
curielmccurielmc

gstack

Control a persistent Playwright headless browser for browser-based QA testing.

Community
Advanced