skills.rest
lemig
lemigCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack

Orchestrate Playwright-driven browser QA tasks and collect screenshots, diffs, and logs.

Updated May 14, 2026
Search Tags:#automation#screenshots#qa#playwright#browser#diffs#daemon
One-click install
npx skills add https://github.com/lemig/transcriptor --skill gstack-lemig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/lemig/transcriptor --skill gstack-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual browser QA toil with a deterministic, local testing workflow that runs against a persistent Playwright daemon.

Core Features & Use Cases

  • Deterministic browser interactions via a local Playwright daemon for repeatable QA runs.
  • Evidence collection: screenshots, diffs, logs, and interaction traces to reproduce bugs.
  • Claude Code integration: trigger browser QA flows from prompts like /qa or /browse and generate test artifacts.

Quick Start

Install gstack, start the local browser daemon, and begin a sample QA flow with a prompt such as "test this page" to see automated results.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate browser QA tasks locally using Playwright?▼

Automate browser QA tasks locally by running a persistent Playwright daemon that orchestrates deterministic headless browser interactions for repeatable test runs. It executes UI verification and form interactions directly against test pages in real environments.

How do I capture screenshots and diffs during automated UI testing?▼

Capture screenshots and diffs during automated UI testing by triggering evidence collection workflows that log interaction traces and visual differences across test pages. This mechanism helps reproduce bugs by storing deterministic test artifacts from real environments.

Can I trigger browser QA flows directly from Claude Code prompts?▼

Yes, you can trigger browser QA flows directly from Claude Code prompts using commands like /qa or /browse. The SKILL.md-driven workflow integrates with the local daemon to execute automated tests and generate interaction artifacts.

What is the best way to run repeatable headless browser tests without manual toil?▼

The best way to run repeatable headless browser tests without manual toil is using a local QA daemon with deterministic scripts and frontmatter-based configuration. This approach ensures consistent UI verification and automated evidence collection across runs.

Do I need a local daemon running to execute Playwright QA workflows?▼

Yes, you need a local daemon running to execute Playwright QA workflows. The daemon maintains persistent browser sessions required for orchestrating headless interactions, capturing screenshots, and collecting logs during test execution.

Related Skills

Explore More Software Engineering Skills→
GTC6244GTC6244

gstack

Run a persistent headless browser daemon for QA testing with Bun and Playwright.

Community
Advanced
nullmastermindnullmastermind
9

spx-e2e-playwright

Reproduce UI bugs in local web apps with Playwright MCP and collect browser evidence.

Community
Advanced
tsenseitsensei
3

gstack

Drive a headless browser to interact with UI and capture annotated screenshots and diffs.

Community
Advanced
florianhornerflorianhorner
4

gstack

Automate browser-based QA workflows via a persistent local browser daemon controlled through a CLI.

Community
Advanced