skills.rest
lyh2
lyh2COMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate QA browser sessions with a deterministic headless Chromium environment.

Updated Apr 3, 2026
Search Tags:#automation#screenshots#qa#diff#playwright#browser
One-click install
npx skills add https://github.com/lyh2/gstack-deepseek --skill gstack-lyh2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/lyh2/gstack-deepseek/tree/main
Command: npx skills add https://github.com/lyh2/gstack-deepseek --skill gstack-lyh2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates AI-driven QA browser sessions by providing a deterministic, reusable headless browser environment that supports navigation, interaction, verification, and evidence capture to speed up bug hunting and deployment validation.

Core Features & Use Cases

  • Navigate pages, interact with elements, verify state, and generate diffs to confirm changes.
  • Capture annotated screenshots, test responsive layouts, and automate forms, uploads, and dialogs.
  • Provide reproducible bug evidence and test progress for deployments, QA cycles, and product exploration.

Quick Start

Open Claude Code and tell it to start a QA session with /browse on the target site.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate QA browser sessions to capture annotated screenshots?▼

You can automate QA browser sessions by running a persistent headless Chromium daemon with Playwright tooling to navigate pages, interact with elements, and capture annotated screenshots as bug evidence.

What is a deterministic headless browser environment for bug hunting?▼

A deterministic headless browser environment provides reproducible browser actions for bug hunts and deployment validation, ensuring consistent navigation, snapshotting, and diffing results across AI-driven QA cycles.

Can I use Playwright to generate diffs and verify deployment changes?▼

Yes, gstack uses Playwright-based tooling to navigate pages, verify state, and generate visual diffs, allowing you to confirm deployment changes and capture reproducible progress.

Does the headless Chromium daemon support responsive layout testing and form automation?▼

The headless Chromium daemon supports testing responsive layouts and automating forms, uploads, and dialogs, providing a reusable environment for comprehensive product dogfooding and QA verification.

What are the limitations of using a persistent Chromium daemon for AI-driven QA?▼

Using a persistent Chromium daemon requires maintaining the background process environment, and its deterministic behavior depends on consistent Playwright-based tooling configurations for accurate snapshotting and diffing.

Related Skills

Explore More Software Engineering Skills→
sajalsuhanesajalsuhane

gstack

Bind Claude Code to a persistent headless Chromium daemon for QA browser sessions.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
UlanxxUlanxx

browse

Drive a persistent Playwright browser for automated web QA and evidence capture.

Community
Advanced
amanikamanik

gstack

Automate headless browser QA workflows with persistent sessions and visual diffs.

Community
Advanced