skills.rest
studyzy
studyzyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack

Orchestrate a persistent Playwright-driven browser for automated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff.

What problem does it solve?

Automates browser-based QA testing by orchestrating a persistent Playwright-driven headless browser, enabling automated navigation, interaction, state validation, and evidence collection for bug repros and deployment verification.

Core Features & Use Cases

  • Persistent QA browser: maintain login state, cookies, and context across commands.
  • Navigate, interact, and read: goto, click, fill, text, html, links, forms, and accessibility snapshots.
  • Verification and evidence: diffs, annotated screenshots, and performance traces to validate changes.
  • Dogfood workflows: fast QA loops integrated into development and PR review for faster shipping.

Quick Start

Invoke /browse to start a headless QA session and test a URL.

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 testing with Playwright from Claude Code?▼

Automate browser QA testing by orchestrating a persistent Playwright-driven headless browser directly from Claude Code to navigate pages, interact with elements, and validate application state.

Can I maintain login state and cookies across multiple browser automation commands?▼

Yes, the persistent QA browser maintains login state, cookies, and context across commands, enabling continuous automated testing workflows without needing to re-authenticate for every action.

What's the best way to collect evidence for bug repros during web app testing?▼

Collect bug repro evidence during web app testing by utilizing automated annotated screenshots, performance traces, and diffs to validate state changes and document failures.

Does automated deployment verification require a local browser daemon to work?▼

Yes, automated deployment verification requires Playwright, a local browser daemon, and a small CLI footprint to execute commands and collect testing artifacts.

How do I validate web app state changes and capture diffs during feature testing?▼

Validate web app state changes by navigating pages and interacting with elements, then capturing automated diffs, screenshots, and accessibility snapshots to verify feature behavior.

When should I not use headless browser automation for QA?▼

Avoid headless browser QA automation when testing requires visual rendering validation across different screen sizes or when your environment lacks support for running a local browser daemon.

Related Skills

Explore More Software Engineering Skills→
lyh2lyh2

gstack

Automate QA browser sessions with a deterministic headless Chromium environment.

Community
Advanced
jm199seojm199seo

browse

Automate QA browser interactions to validate web workflows and capture evidence.

Community
Advanced
softmgsoftmg

github-workflow-automation

Automate GitHub Actions workflow generation and CI/CD pipeline management.

Official
Advanced
rlagycksrlagycks
3

browser-qa

Automates visual, functional and accessibility testing of web pages via Playwright or Puppeteer scripts.

Community
Intermediate