skills.rest
antriksh-29
antriksh-29COMMUNITY
Explore all skills by this author →
GitHub

gstack

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

Updated Mar 24, 2026
Search Tags:#automation#qa#cli#playwright#browser#dogfood#gstack
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill gstack-antriksh-29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill gstack-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Enables Claude Code to perform QA testing and site dogfooding using a persistent headless browser, removing setup friction and flaky test scenarios.

Core Features & Use Cases

  • Persistent browser daemon: Open and reuse a Chromium session across commands to maintain cookies and login state.
  • Snapshot, diff, and annotated screenshots: Visual verification tools to compare pages and highlight changes.
  • Cookie management & authenticated testing: Seamless testing across multiple workspaces with persistent cookies and sessions.
  • Workspace isolation: Independent browser instances per workspace for parallel QA workflows.
  • CLI-driven browser control: Automate navigation, form interactions, text extraction, and assertions from prompts and scripts.

Quick Start

Install gstack, then invoke /browse to start a persistent headless QA workflow.

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 a persistent session?▼

You can automate headless browser QA testing by launching a persistent Chromium daemon via a CLI, which maintains cookies and login state across multiple commands and workspaces for reliable testing.

What is visual diff testing and how does it help with site dogfooding?▼

Visual diff testing compares browser snapshots to highlight changes on web pages. It helps site dogfooding by automatically capturing annotated screenshots to visually verify UI updates and catch regressions.

Can I run parallel QA workflows with workspace isolation in a headless browser?▼

Yes, you can run parallel QA workflows using workspace isolation. The tool spawns independent browser instances per workspace, ensuring separated sessions, cookies, and testing environments for concurrent execution.

Do I need Playwright to perform form interactions and text extraction in CI workflows?▼

The tool uses a Playwright-powered Chromium daemon to handle form interactions and text extraction. It is designed for local development and CI-like workflows, exposing browser commands via HTTP for automation.

How do I manage cookies for authenticated testing across multiple workspaces?▼

Cookie management for authenticated testing is handled automatically by the persistent browser daemon. It retains cookies and login sessions across commands, enabling seamless testing across multiple isolated workspaces.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

gstack

Automate website testing and deployment verification with persistent headless browser control.

Community
Advanced
rahmanayonrahmanayon

browse

Automate QA browser testing by navigating URLs, interacting with elements, and capturing annotated screenshots.

Community
Advanced
BuilderIOBuilderIO
11

playwright-cli

Automate browser interactions and Playwright test workflows via command-driven tooling.

Official
Advanced
ulpi-ioulpi-io
13

browse

Automate browser and native app UI interactions across Chromium and native runners.

Official
Advanced