skills.rest
scanbott
scanbottCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Drive a headless browser to navigate pages, interact with elements, and capture screenshots and diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack enables teams to automate QA testing and bug evidence collection by providing a persistently running headless browser that can navigate pages, interact with UI, capture diffs, and annotate screenshots. This reduces manual steps in reproducing bugs and regression testing.

Core Features & Use Cases

  • Interactive navigation and form interaction in a headless browser.
  • Snapshot-based refs and annotated screenshots for bug reports.
  • Diffing before/after pages to verify changes in CI or QA.

Quick Start

Trigger a quick QA session by instructing the browser to goto a test URL, capture a snapshot, and take a screenshot.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate QA testing with a headless browser to capture screenshots and diffs?▼

Automated QA testing uses a headless browser to navigate pages, interact with UI elements, and capture snapshot-based references alongside annotated screenshots for bug reproduction and regression validation.

Can I use a headless browser to reproduce bugs and collect evidence from live sites?▼

Yes, a headless browser can navigate live sites or local HTML, interact with forms, and capture annotated screenshots to reduce manual steps in reproducing bugs and collecting visual evidence for reports.

How do I diff before and after pages to verify UI changes in a QA workflow?▼

Page diffing captures snapshots before and after changes to visually verify UI updates. This headless browser automation validates design modifications across test harnesses or live URLs in regression workflows.

What do I need to run automated screenshot capture and browser interaction for QA testing?▼

Automated screenshot capture and browser interaction require Bash, Read, and AskUserQuestion tools to drive the headless browser, execute navigation, and handle user input during QA session planning and execution.

When should I use headless browser automation for design review demos?▼

Use headless browser automation for design review demos when you need to navigate pages, capture annotated screenshots, and validate visual changes without manual browser interaction or local GUI overhead.

Related Skills

Explore More Software Engineering Skills→
fghaffarfghaffar

browse

Automate end-to-end QA testing of web applications via headless Chromium.

Community
Advanced
JaykaijackJaykaijack

browse

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

Community
Advanced
t0labt0lab
2

playwright

Automate browser interactions and UI verification via Playwright CLI snapshots.

Official
Intermediate
hffmnnjhffmnnj
39

visual-regression

Compare screenshots pixel-by-pixel to detect unintended UI changes.

Community
Intermediate