gstack

Control a persistent headless Chromium browser for automated QA testing.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill gstack-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill gstack-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual browser testing is slow, error-prone, and impossible to scale across deployments and devices. AI agents need reliable programmatic browser control to verify sites, test user flows, and capture visual evidence without manual clicking or flaky human observation.

Core Features & Use Cases

  • Persistent Headless Browser: Auto-starts a Chromium daemon in ~3 seconds, then executes commands in ~100-200ms. Cookies, tabs, and login sessions persist between calls for seamless multi-step testing.
  • Element Interaction & Verification: Navigate pages, click/fill/select elements using accessibility refs, verify element states (visible, enabled, checked), and diff page changes after interactions to confirm they worked.
  • Visual Bug Capture: Take screenshots in multiple modes (full page, viewport, element crop, region clip, base64), generate annotated screenshots with ref labels, and test responsive layouts across mobile, tablet, and desktop viewports.
  • Form & Upload Testing: Test file uploads, fill complex forms, handle dialogs with auto-accept/dismiss, and capture console errors and network requests to catch silent failures.
  • Use Case: A developer deploying a new feature can automatically verify the staging URL loads correctly, screenshots render properly on all device sizes, the login flow completes without errors, and no console warnings appear — all in seconds without manual clicking.

Quick Start

Navigate to your staging URL and take a screenshot to verify the deployment looks correct.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate browser QA testing for deployment verification?

A persistent headless Chromium browser automates site verification by maintaining cookies and login sessions across calls, allowing you to execute multi-step user flows and capture visual evidence without manual clicking.

Can I capture screenshots across different device viewports with Playwright?

Yes, you can test responsive layouts across mobile, tablet, and desktop viewports by capturing screenshots in full page, viewport, or element crop modes using a headless Chromium browser compiled with Playwright.

Does headless browser automation work for testing complex forms and file uploads?

Headless browser automation supports testing file uploads and complex forms by filling elements, handling dialogs with auto-accept/dismiss, and capturing console errors and network requests to identify silent failures.

How do I verify element states during site verification?

You can verify element states by clicking, filling, and selecting elements using accessibility refs, then checking visibility and enabled states, and diffing page changes after interactions to confirm successful execution.

Do I need Bun to run headless browser commands for visual bug capture?

Yes, executing headless browser commands for visual bug capture requires the browse binary compiled with Bun and Playwright to achieve sub-second latency and maintain persistent session state across testing calls.