gstack

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill gstack-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill gstack-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manual browser testing is slow, repetitive, and difficult to document consistently. QA engineers and developers waste hours clicking through flows, taking screenshots, and trying to reproduce bugs across different viewports and authentication states.

Core Features & Use Cases

  • Persistent Headless Browser: Sub-second browser commands with state persistence across sessions (cookies, tabs, login state).
  • Ref-Based Interaction: Click, fill, and verify elements using accessibility-tree refs instead of fragile CSS selectors.
  • Visual Verification: Annotated screenshots, before/after diffs, responsive layout testing, and element-level cropping.
  • Form & Dialog Testing: Automated form filling, validation checking, file uploads, and dialog handling with auto-accept.
  • Authenticated Testing: Import real browser cookies to test gated pages without manual re-login.
  • Multi-Step Workflows: Chain commands into efficient batches for complete user flow testing.

Quick Start

Use the gstack browse skill to open https://staging.example.com, walk through the checkout flow, take annotated screenshots of each step, and report any visual or functional issues discovered.

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 for staging deployments?

Automate browser QA testing for staging deployments by executing persistent headless Chrome sessions to walk through user flows, capture annotated screenshots, and report visual or functional issues. You can chain commands into efficient batches for complete multi-step workflow testing.

Can I test authenticated pages without manual re-login using headless Chrome?

Yes, you can test authenticated pages without manual re-login by importing real browser cookies into the persistent session. State persistence across sessions maintains cookies, tabs, and login state for automated testing of gated pages.

How do you handle visual regression detection across different viewports?

Visual regression detection across different viewports is handled by capturing annotated screenshots, generating before/after diffs, and performing responsive layout testing. Element-level cropping allows precise visual verification of specific components.

Do I need Playwright installed to run cross-browser visual verification?

Yes, you need a Playwright-managed Chromium daemon to run cross-browser visual verification. The environment also requires a compiled Bun binary to execute persistent browser sessions, ref-based element selection, and network or console monitoring.

How do I select elements for web testing without fragile CSS selectors?

Select elements for web testing using accessibility-tree refs instead of fragile CSS selectors. Ref-based interaction allows you to click, fill, and verify elements consistently during form validation, file uploads, and dialog handling with auto-accept.