skills.rest
filipnyquist
filipnyquistCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack

Control a persistent Playwright browser daemon for automated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating, testing, and debugging web apps with AI agents by providing a fast, persistent headless browser daemon that maintains state across commands.

Core Features & Use Cases

  • QA automation: automate navigation, interaction, verification, and bug evidence collection across pages, forms, and dialogs.
  • Site dogfooding: replay user flows on deployments and collect annotated evidence for quick reporting.
  • Evidence-rich debugging: generate diffs and annotated screenshots to document changes and failures.

Quick Start

Launch the headless browser, navigate to a page, and capture a screenshot for bug reporting.

Frequently Asked Questions about gstack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser testing with Playwright using a persistent state?▼

Automating browser testing with a persistent state involves using a fast Playwright-based headless daemon that maintains state across commands, enabling rapid navigation, interaction, and stateful verification across multiple pages.

Can I capture annotated screenshots for bug evidence during QA automation?▼

Capturing annotated screenshots for bug evidence is supported through dedicated commands, allowing you to generate diffs and document UI failures quickly during site dogfooding and automated testing workflows.

What is the best way to run stateful CLI testing across web pages?▼

Stateful CLI testing across web pages is best handled by a persistent headless browser server that isolates per-workspace environments, executes deterministic tasks, and supports idle shutdown for downstream workflows.

Do I need any external dependencies to run this AI-driven QA tool?▼

No external dependencies are required to run this AI-driven QA tool. It operates independently using a fast Playwright-based browser daemon to control navigation, interaction, and verification without additional packages.

How does site dogfooding work with AI-driven browser automation?▼

Site dogfooding with AI-driven browser automation works by replaying user flows on deployments using commands like goto, click, and snapshot, collecting annotated evidence to verify UI changes and report failures.

Related Skills

Explore More Software Engineering Skills→
tropekstropeks

benchmark

Measure web performance metrics and compare them against baselines.

Community
Advanced
danabramsdanabrams
3

gromit-debug

Identify root causes of bugs and generate structured investigation reports.

Community
Advanced
pyinxpyinx
14

webapp-testing

Automate end-to-end testing of local web applications with Python Playwright.

Community
Intermediate
jm199seojm199seo

gstack

Automates QA testing with a persistent Chromium headless browser and workflow commands.

Community
Advanced