skills.rest
txema-puch
txema-puchCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Run a persistent Playwright browser daemon for automated QA and evidence capture.

1|Updated Mar 23, 2026
Search Tags:#automation#cli#playwright#browser#headless#dogfooding#qa-testing
One-click install
npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill gstack-txema-puch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/txema-puch/drone-ai-saturdays/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill gstack-txema-puch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast, persistent headless browser daemon that QA teams and product teams can use to automate page interactions, capture evidence, and validate flows across environments.

Core Features & Use Cases

  • Navigate pages, interact with elements, read state, and capture artifacts (text, HTML, screenshots, network logs) for reproducible QA reports.
  • Diff, annotate, and compare snapshots to verify that UI changes have the intended effect; test responsive layouts, forms, uploads, dialogs, and dynamic content.
  • Use for dogfooding user flows during development, internal QA, and demos, ensuring experiences are verified early.

Quick Start

Load a URL in the browse daemon, perform actions, and generate evidence (state diffs and annotated screenshots) with a single instruction.

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 interactions for QA testing?▼

Capture QA testing evidence like screenshots and network logs by navigating pages with a persistent headless browser daemon that reads state and generates structured artifacts for reporting.

Can I use Playwright to capture screenshots and network logs for automated QA?▼

Yes, you can use Playwright-based browsing to navigate pages, interact with elements, and capture structured evidence including screenshots, text, HTML, and network logs for reliable QA testing.

What is the best way to diff and compare UI snapshots during development?▼

The best way to diff and compare UI snapshots is to capture page states, annotate them, and compare snapshots to verify that UI changes have the intended effect across responsive layouts and dynamic content.

How do I validate internal dashboard flows through automated dogfooding?▼

Validate internal dashboard flows through automated dogfooding by executing deterministic browser actions on web apps and internal tools, then capturing verifiable artifacts to ensure experiences are verified early.

Does this headless browser CLI support testing dynamic content and form uploads?▼

Yes, the headless browser CLI supports testing dynamic content, forms, uploads, and dialogs by applying deterministic browser actions to capture reproducible evidence across different environments.

Why use a persistent browser daemon instead of standard browser automation scripts?▼

Use a persistent browser daemon instead of standard scripts to maintain fast, deterministic browser actions across environments, enabling reliable evidence capture and structured state diffs for QA reporting.

Related Skills

Explore More Software Engineering Skills→
lyh2lyh2

gstack

Automate QA browser sessions with a deterministic headless Chromium environment.

Community
Advanced
BradliebsBradliebs

gstack

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

Community
Advanced
miketrombamiketromba
1

agent-browser

Automate browser interactions for testing, form filling, and data extraction.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

gstack

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

Community
Advanced