skills.rest
cegit27
cegit27OFFICIAL
Explore all skills by this author →
GitHub

gstack

Automate browser-based QA testing with persistent headless Chromium sessions.

3|14|Updated Mar 10, 2026
Search Tags:#browser automation#playwright#headless browser#qa testing#screenshot testing#site dogfooding
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-cegit27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual browser testing is slow, repetitive, and hard to reproduce. This skill gives Claude Code a persistent headless Chromium browser that can navigate pages, interact with elements, verify state, and capture visual evidence automatically, eliminating hours of manual clicking and screenshotting.

Core Features & Use Cases

  • Persistent Browser State: The browser stays alive between commands, preserving cookies, login sessions, and tabs across the entire testing session.
  • Ref-Based Interaction: Uses accessibility tree refs like @e1 and @e2 instead of fragile CSS selectors, making element targeting reliable even when the page changes.
  • Visual Verification: Take annotated screenshots, diff before/after snapshots, test responsive layouts, and capture bug evidence with element highlighting.
  • Use Case: A developer can ask Claude to test their staging deployment, and Claude will automatically navigate to the site, take a snapshot, click through the login flow, verify the dashboard loads, and screenshot any issues found.

Quick Start

Use the gstack browse skill to test your web application by navigating to any URL, interacting with page elements through labeled refs, and capturing screenshots to verify the user flow works correctly.

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 and capture screenshots of user flows?▼

Automating browser QA testing involves using a persistent headless Chromium session to navigate pages, interact with elements, and capture screenshots. This skill maintains browser state and cookies across commands to verify user flows and capture bug evidence automatically.

Can I use Playwright to verify deployment health checks without writing test scripts?▼

Playwright is utilized by this skill to execute navigation, interaction, and snapshot commands via Bash tool calls. It automates deployment health checks by navigating to your staging site, verifying the dashboard loads, and screenshotting any issues found without manual scripting.

How does headless browser automation handle responsive layout testing and form validation?▼

Headless browser automation handles responsive layout testing and form validation by applying persistent Chromium sessions to interact with page elements. It uses accessibility tree refs like @e1 instead of fragile CSS selectors, ensuring reliable element targeting even when the page changes.

What is the best way to test site dogfooding workflows automatically?▼

Testing site dogfooding workflows automatically is best achieved through persistent headless browser sessions that preserve login states. This skill automates the process by navigating URLs, taking snapshots, clicking through flows, and capturing visual evidence of the application state.

Do I need to install specific dependencies to run headless browser automation for QA testing?▼

Running headless browser automation for QA testing requires the gstack browse binary and Playwright to execute commands. These dependencies are necessary to enable persistent browser state, accessibility tree ref interactions, and visual verification snapshots.

Why does persistent browser state matter for automated screenshot testing?▼

Persistent browser state matters for automated screenshot testing because it keeps the browser alive between commands, preserving cookies, login sessions, and tabs. This eliminates the need to repeatedly authenticate, ensuring accurate user flow verification across the entire testing session.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

setup-browser-cookies

Import authenticated Chromium session cookies into a headless Playwright environment.

Community
Intermediate
IsKenKenYaIsKenKenYa

prototype

Create throwaway in-memory prototypes to validate state models or UI variants.

Community
Basic
Michae2xlMichae2xl

deployment-patterns

Guide web application deployment with CI/CD pipelines, Docker, and health checks.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack

Automate persistent headless browser QA testing with Playwright and Chromium.

Community
Advanced