skills.rest
zhifengzhang-sz
zhifengzhang-szCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Run a persistent headless browser daemon for QA testing and evidence capture.

Updated Feb 27, 2026
Search Tags:#automation#testing#qa#cli#playwright#browser#headless
One-click install
npx skills add https://github.com/zhifengzhang-sz/divine-book --skill gstack-zhifengzhang-sz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/zhifengzhang-sz/divine-book/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/zhifengzhang-sz/divine-book --skill gstack-zhifengzhang-sz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Core Features & Use Cases

  • Navigate pages, interact with elements, verify state, and diff results across sessions.
  • Take annotated screenshots, test responsiveness, and capture bug evidence for PRs.
  • Use when you need to open, verify, or dogfood a deployment with a fast, persistent browser.

Quick Start

Launch the persistent browse daemon and start a QA session with a single command.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I run headless browser QA testing across multiple sessions?▼

Headless browser QA testing across sessions requires a persistent browser daemon that maintains state. This skill provides a long-running headless environment to enable navigation, interaction, and diffing across continuous development pipeline sessions.

Can I capture annotated screenshots for bug evidence using Playwright?▼

Yes, capturing annotated screenshots for bug evidence is fully supported. You can navigate pages, interact with elements, and take annotated screenshots to document visual states and file comprehensive bug reports for your pull requests.

What is the best way to verify a deployment and dogfood user flows with a CLI?▼

Verifying a deployment and dogfooding user flows is best handled by a lightweight CLI controlling a persistent headless browser. This approach allows you to quickly test responsive layouts, forms, and dialogs to ensure deployment reliability.

Does this testing skill support diffing before and after page interactions?▼

Yes, diffing before and after page interactions is a core feature. The skill enables deterministic parsing and state verification, allowing you to compare page states across sessions and capture precise evidence of changes or bugs.

When do I need a persistent headless browser daemon for site testing?▼

You need a persistent headless browser daemon when you require reliable, reproducible browser-based QA. It is essential for fast iteration in development pipelines, allowing continuous navigation, interaction, and evidence collection without restarting the browser.

Related Skills

Explore More Software Engineering Skills→
djnsty23djnsty23
2

agent-browser

Automates browser tasks via a Rust CLI with a Node.js daemon and Playwright backend.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
haxlyshaxlys

vercel-sandbox

Run agent-browser with headless Chromium inside Vercel Sandbox microVMs.

Community
Intermediate