gstack

Name: gstack
Availability: InStock
Author: Martin

Automate end-to-end QA checks on web pages with a headless browser.

1|Updated Apr 8, 2026

Search Tags:#automation #screenshots #qa #web-testing #headless

Ready to run

npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill gstack-martin-hsu-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/martin-hsu-test/gstack-gemini-slim/tree/main/.gemini/skills/gstack
Command: npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill gstack-martin-hsu-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, reliable QA checks and bug evidence collection are tedious to do manually. gstack provides a fast headless browser to automate site opening, interaction, diffing, and screenshot capture for QA cycles.

Core Features & Use Cases

Traverse pages, interact with elements, verify state, and diff before/after to spot regressions.
Take annotated screenshots and test responsive layouts, forms, uploads, and dialogs to capture evidence for bugs.
Use in workflows like opening deployments, dogfooding user flows, or filing bug reports with visual evidence.

Quick Start

Launch a QA session by opening a site and running a basic gstack QA task.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate end-to-end QA checks for web pages?▼

Automate end-to-end QA checks for web pages by using a headless browser to open sites, interact with elements, verify states, and diff changes to spot regressions. It generates reproducible artifacts for bug evidence.

Can I capture annotated screenshots during automated web testing?▼

Yes, you can capture annotated screenshots during automated web testing. The headless browser traverses pages, interacts with elements, and captures visual evidence for bug reports and regression tracking.

How do I test responsive layouts, forms, and dialogs without a GUI?▼

Test responsive layouts, forms, and dialogs without a GUI by running a headless browser that navigates and interacts with page elements. It validates conditions and captures bug evidence artifacts.

What is the best way to collect bug evidence for web page regressions?▼

The best way to collect bug evidence for web page regressions is automating a headless browser to diff before and after states. It takes annotated screenshots and captures reproducible artifacts for filing reports.

Does headless browser testing work for dogfooding user flows and deployments?▼

Yes, headless browser testing works for dogfooding user flows and deployments. It opens sites, verifies page states, interacts with elements, and generates reproducible artifacts to validate functionality.

Can I verify page state and diff changes in an automated QA cycle?▼

Yes, you can verify page state and diff changes in an automated QA cycle. The headless browser traverses pages, interacts with elements, validates conditions, and spots regressions by diffing before and after states.