gstack

Name: gstack
Availability: InStock
Author: Yaugourt

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

2|2|Updated Dec 1, 2024

Search Tags:#automation #workflow #qa #playwright #headless #claude-code #browse

Ready to run

npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill gstack-yaugourt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill gstack-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, deterministic headless browser workflow for QA, dogfooding, and bug reporting with Claude Code, replacing brittle manual steps.

Core Features & Use Cases

Persistent browser daemon that you can reuse across commands like goto, click, text, and snapshot.
Diff, annotate, and screenshot capabilities to verify changes and collect bug evidence.
Support for responsive testing, forms, uploads, dialogs, and real-world user flows.

Quick Start

Start a headless browser session and issue simple QA commands to navigate, interact, and capture 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 with Claude Code?▼

Automate headless browser QA with Claude Code by starting a persistent browser daemon, then issuing commands to navigate pages, interact with UI elements, and capture annotated screenshots to validate state.

Can I capture screenshots and diff UI changes in a headless browser workflow?▼

Yes, you can capture screenshots and diff UI changes in a headless browser workflow; the daemon annotates screenshots and verifies state differences to collect bug evidence across responsive layouts, forms, and dialogs.

Does gstack support testing real-world user flows like forms and uploads?▼

Yes, gstack supports testing real-world user flows like forms, uploads, and dialogs; the daemon navigates pages, interacts with UI elements, and validates state across responsive layouts to simulate actual user behavior.

How do I run responsive layout testing using a headless browser daemon?▼

Run responsive layout testing by starting the persistent headless browser daemon and issuing navigation and snapshot commands; it captures annotated screenshots across different responsive layouts to verify UI state.

What's the best way to do site dogfooding and bug reporting with Claude Code?▼

The best way to do site dogfooding and bug reporting with Claude Code is using a fast headless browser daemon to navigate pages, validate state, diff changes, and capture annotated screenshots as bug evidence.

Why use a persistent headless browser daemon instead of manual QA steps?▼

Use a persistent headless browser daemon instead of manual QA steps to replace brittle manual processes with deterministic automation, reusing a single browser session across multiple navigation, interaction, and snapshot commands.