skills.rest
curielmc
curielmcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack

Control a persistent Playwright headless browser for browser-based QA testing.

Updated Feb 27, 2026
Search Tags:#automation#testing#qa#playwright#browser#headless#screenshot
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill gstack-curielmc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/curielmc/beat-SPY --skill gstack-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, persistent headless browser for automated QA testing, site dogfooding, and bug reproduction. It streamlines browser-based verification with a stable runtime and a rich command surface.

Core Features & Use Cases

  • Persistent headless browser powered by Playwright for reliable, repeatable QA sessions.
  • Snapshot, diff, and annotate workflows to verify changes and generate evidence.
  • Automated interactions (goto, click, fill, type, wait) and visual checks (screenshot, responsive) across test flows.

Quick Start

Start a QA session by invoking the browse workflow and testing a site end-to-end with real browser interactions.

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 and site dogfooding?▼

Automate QA testing by controlling a persistent headless browser to navigate, click, fill, and verify state across test flows. It runs locally as a Bun-based daemon using Playwright, streamlining site dogfooding and bug reproduction.

Can I capture annotated screenshots and visual diffs during automated browser testing?▼

Yes, visual diffs and annotated screenshots are supported during automated browser testing. The Skill provides snapshot, diff, and annotate workflows to verify changes and generate evidence within your test flows.

Does this Playwright headless browser support responsive testing across different viewport sizes?▼

Yes, responsive testing across different viewport sizes is supported. You can use the responsive command to verify site rendering and behavior across various screen dimensions during your test flows.

What is the best way to run persistent headless browser sessions for bug reproduction?▼

The best way to run persistent headless browser sessions is using a Bun-based daemon with Playwright. This approach maintains a stable runtime for reliable, repeatable QA sessions and consistent bug reproduction.

What browser interactions are available for headless QA automation?▼

Available browser interactions for headless QA automation include goto, click, fill, type, and wait. These commands automate element interaction and state verification across end-to-end test flows.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

gstack

Automate browser QA with a persistent headless Chromium daemon.

Community
Advanced
akiyoshiakiyoshi

qa

Automate end-to-end testing and generate structured QA reports with health scores.

Community
Advanced
pythoninthegrassespythoninthegrasses
1

deployment-pipeline-design

Design multi-stage CI/CD pipelines with approval gates and deployment strategies.

Official
Advanced
pacphipacphi
6

compatibility-testing

Validate web applications across browsers, devices, and cloud platforms with Playwright.

Community
Advanced