skills.rest
pcaokhai
pcaokhaiCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate browser-based QA tasks with a persistent Chromium daemon.

Updated Mar 24, 2026
Search Tags:#automation#testing#qa#playwright#browser#headless
One-click install
npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill gstack-pcaokhai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/pcaokhai/gradion-response-report-api/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill gstack-pcaokhai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

gstack addresses the friction of QA testing and production dogfooding by providing a fast, persistent, headless browser automation layer. It lets you reliably test navigation, interactions, and UI states across deployments, capture evidence, and iterate quickly without flakiness or repeated setup.

Core Features & Use Cases

  • Persistent Chromium daemon enabling sub-second tool calls after initial startup.
  • Commands for navigate, read, interact, read state, diff, screenshot, responsive, cookies, dialogs, and more.
  • Evidence capture: annotated screenshots and logs for bug reports and PRs.
  • Multi-workspace isolation and per-repo state; supports QA/test across branches.

Quick Start

Launch gstack and run a browse command against a URL to verify a user flow end-to-end.

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 across deployments?▼

Headless browser QA testing is automated using a persistent Chromium daemon that executes navigation, interactions, and state checks across deployments. It captures annotated screenshots and logs as evidence for bug reports and PRs.

Can I integrate browser automation commands into my CI workflows?▼

Browser automation commands can be integrated into CI workflows through a stable CLI command surface. The CLI exposes QA workflows for navigation, interaction, and state verification directly within automated pipelines.

How does a persistent Chromium daemon improve testing speed?▼

A persistent Chromium daemon improves testing speed by keeping the browser active in the background, enabling sub-second tool calls after the initial startup. This removes repeated browser launch overhead during QA testing.

What is the best way to isolate QA testing state across multiple branches?▼

QA testing state across multiple branches is isolated using multi-workspace isolation features. This provides per-repo state management, allowing you to run tests and capture evidence independently for each branch.

What kind of evidence can I capture for bug reports during UI testing?▼

Evidence for bug reports during UI testing is captured as annotated screenshots and logs. This visual and textual proof documents UI states and interactions, directly linking failures to bug reports and pull requests.

Does this headless browser tool support dialogs and cookies management?▼

The headless browser tool supports dialogs and cookies management alongside core navigation and interaction commands. These features allow you to simulate and verify complex user sessions during site dogfooding.

Related Skills

Explore More Software Engineering Skills→
ShmurdocShmurdoc

gstack

Automate headless Chromium browser control for QA testing and site verification.

Community
Advanced
bcascibcasci
3

draft-github-issues

Convert unstructured plans into structured GitHub issue YAML files.

Community
Intermediate
rkumar261rkumar261
1

gstack

Drive a headless browser to navigate pages, interact with UI elements, and verify state.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

gstack

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

Community
Advanced