gstack

Control a headless browser to verify page state and capture annotated screenshots.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill gstack-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/yckkkk/reo --skill gstack-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, and capture bug evidence.

Core Features & Use Cases

  • Navigate pages, interact with elements, verify state, and diff before/after to identify changes.
  • Take annotated screenshots and test responsive layouts, forms, uploads, and dialogs to validate deployments and dogfood user flows.
  • Use in QA workflows to reproduce bugs, validate deployments, and gather evidence for fixes.

Quick Start

Open a URL with gstack browse and capture a screenshot to start validating page behavior.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I capture annotated screenshots for bug reproduction using a headless browser?

You can capture annotated screenshots for bug reproduction by running a headless browser to navigate pages, interact with elements, and save visual evidence of the page state. This automates gathering bug evidence for fixes.

Can I test responsive layouts and form uploads with automated QA testing?

Automated QA testing can validate responsive layouts, form uploads, and dialogs by controlling a headless browser. It interacts with these elements directly to verify page behavior and capture deployment validation evidence.

What is the best way to diff before and after states during site testing?

Diffing before and after states during site testing is handled by navigating pages with a headless browser and comparing the verified page states. This identifies changes and validates deployments across modern web apps.

Does headless browser automation work for dogfooding user flows?

Headless browser automation supports dogfooding user flows by navigating pages and interacting with elements to verify state. It captures visual evidence and validates behaviors across modern web apps without manual browsing.

How do I start validating page behavior for deployment validation?

To start validating page behavior for deployment validation, open a URL with the browse command and capture a screenshot. This initiates the headless browser to verify state and gather evidence for your site testing.