gstack

Execute headless browser QA workflows with screenshots and console errors.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill gstack-tumeloramaphosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill gstack-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The gstack Skill removes the guesswork and tedium of manual QA and site verification by giving your AI a persistent headless browser that can navigate, interact, and collect hard evidence (screenshots, diffs, console/network errors) in a repeatable workflow.

Core Features & Use Cases

  • Persistent headless Chromium: keeps cookies, tabs, and sessions between commands so re-testing doesn’t start from scratch.
  • Evidence-first QA: navigate to pages, verify visible state, capture annotated screenshots, and generate before/after diffs.
  • Real interaction coverage: supports snapshots with element references, responsive layout checks, form filling, uploads, and dialog handling.

Quick Start

Open the target page and run the skill’s browser to navigate and snapshot the interactive elements for verification.

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 to capture screenshots and console errors?

You can automate headless browser QA by using a persistent Chromium daemon to navigate pages, interact with UI elements via ref-based selection, and capture annotated screenshots alongside console and network errors. This workflow provides verifiable evidence for debugging and regression testing.

What is ref-based element selection and how does it work for UI verification?

Ref-based element selection is a mechanism used during headless browser QA where interactive elements are assigned references in a snapshot. This allows precise interaction with UI components like forms and dialogs, ensuring accurate and repeatable UI verification across testing sessions.

Can I keep browser sessions and cookies persistent between headless testing commands?

Yes, you can keep browser sessions, cookies, and tabs persistent between commands. The headless browser uses a persistent daemon architecture, meaning re-testing does not start from scratch and maintains state across multiple navigation and interaction steps.

How do I generate before and after diffs for regression verification?

To generate before and after diffs for regression verification, navigate to the target page and capture an initial annotated screenshot. After making changes, capture another screenshot and the tool will produce a visual diff to highlight UI regressions and layout shifts.

Do I need a compiled browse binary to run responsive screenshot checks?

Yes, a compiled browse binary is required to run responsive screenshot checks. The binary powers the persistent headless Chromium daemon responsible for navigating pages, handling dialogs, and capturing annotated screenshots across different responsive layouts.

What is the best way to reproduce UI issues with network and console error evidence?

The best way to reproduce UI issues is to use a headless browser to navigate the affected pages, interact with elements, and automatically collect console and network errors alongside annotated screenshots. This evidence-first approach ensures repeatable debugging workflows.