skills.rest
lucas-flatwhite
lucas-flatwhiteCOMMUNITY
Explore all skills by this author →
𝕏@lucas_flatwhiteGitHub

gstack

Drive a headless browser to test pages and capture evidence.

43|7|Updated Mar 13, 2026
Search Tags:#automation#testing#qa#evidence#browser#headless#dogfooding
One-click install
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill gstack-lucas-flatwhite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main
Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill gstack-lucas-flatwhite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, reliable way to run QA and dogfood workflows by controlling a headless browser to test pages, verify states, and capture evidence.

Core Features & Use Cases

  • Navigate pages, interact with elements, verify state, and diff before/after.
  • Annotated screenshots, responsive testing, forms, uploads, and dialogs to collect bug evidence.
  • Acts as a downstream reference for upstream gstack workflows in local/CI environments.

Quick Start

Type the gstack trigger to activate a deterministic QA browser session and begin testing.

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 bug evidence?▼

Automating QA testing with a headless browser involves driving page navigation, element interaction, and state verification to capture annotated screenshots and diffs as bug evidence. This Skill automates those deterministic workflows locally or in CI.

Can I use Playwright and Bun to run deterministic responsive testing for forms and uploads?▼

Yes, you can run deterministic responsive testing for forms and uploads using Bun and Playwright. This Skill relies on that stack to drive a fast headless browser, verify states, and handle dialogs in local or CI environments.

What is the best way to capture before and after diffs during browser QA workflows?▼

Capturing before and after diffs during browser QA workflows is best done by driving a headless browser to interact with elements and verify state changes. This Skill automates that process to collect visual bug evidence.

Does this headless QA browser support dogfooding workflows in a CI environment?▼

Yes, this headless QA browser supports dogfooding workflows in a CI environment. It acts as a downstream reference for upstream gstack execution, running deterministic tasks to navigate pages and collect evidence.

How do I start a deterministic QA browser session for page navigation and state verification?▼

To start a deterministic QA browser session for page navigation and state verification, you activate the gstack trigger. This initiates an automated headless browser session for testing pages and capturing evidence.

Related Skills

Explore More Software Engineering Skills→
filipnyquistfilipnyquist

browse

Drive a headless browser to automate QA tasks on web apps.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
aporto-techaporto-tech

gstack-browse

Automate QA testing of web pages with a headless browser.

Official
Intermediate
Jesse-L-MJesse-L-M

gstack

Drive a persistent headless browser via CLI for QA testing.

Community
Advanced