skills.rest
kinetas
kinetasCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate browser-based QA workflows with a persistent headless Chromium daemon.

Updated Mar 11, 2026
Search Tags:#browser automation#Playwright#QA#Claude Code#headless chrome#gstack
One-click install
npx skills add https://github.com/kinetas/ai_coding_web --skill gstack-kinetas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/kinetas/ai_coding_web/tree/main/gstack
Command: npx skills add https://github.com/kinetas/ai_coding_web --skill gstack-kinetas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

gstack provides a self-contained skill that automates a persistent headless browser workflow for Claude Code, reducing setup friction and enabling deterministic QA, design dogfooding, and regression verification.

Core Features & Use Cases

  • Persistent browser daemon: A long-running Chromium instance that retains cookies, sessions, and state across commands.
  • Deterministic tasks: Supports goto, click, fill, snapshot, diff, and annotations to reproduce bugs and verify fixes.
  • Evidence generation: Produces annotated screenshots, diff reports, and textual outputs suitable for PRs and test records.
  • Workflow integration: Powers end-to-end QA, review, and ship workflows by providing reliable browser automation capabilities to Claude Code.

Quick Start

Start a browse session in Claude Code and issue a browse command to begin dogfooding a site.

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 workflows in Claude Code?▼

Automate browser-based QA workflows in Claude Code by loading gstack, which provides a persistent headless browser daemon to coordinate navigation, interaction, and verification across pages.

How do I generate visual evidence and diffs for bug reproduction?▼

Generate visual evidence for bug reproduction using browser automation to produce annotated screenshots, diff reports, and textual outputs suitable for pull requests and test records.

Can I use a persistent headless Chrome instance for deterministic testing?▼

Yes, you can use a persistent headless Chrome daemon that retains cookies, sessions, and state across commands to execute deterministic testing tasks like goto, click, fill, and snapshot.

Does gstack work with Playwright for design reviews?▼

gstack integrates with Claude Code contexts to power design reviews and regression verification by providing reliable browser automation, supporting on-demand browsing tasks with minimal setup.

What is the best way to retain browser sessions across multiple automation commands?▼

Retain browser sessions across multiple automation commands by running a long-running Chromium instance daemon that preserves cookies and state, ensuring deterministic QA and design dogfooding.

Why do I need a persistent browser daemon for regression verification?▼

A persistent browser daemon is needed for regression verification to maintain session state across commands, enabling reliable navigation, interaction, and diff generation for verifying fixes.

Related Skills

Explore More Software Engineering Skills→
konneh-hubkonneh-hub

vercel-sandbox

Run headless Chrome browser automation inside Vercel Sandbox microVMs.

Community
Advanced
bizzybaebizzybae

browse

Automate QA testing with a headless browser for navigation, interaction, and screenshots.

Community
Intermediate
zz8011zz8011

gstack

Provision a persistent headless Chromium daemon for browser-based QA testing.

Community
Advanced
betaTridentbetaTrident

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced