skills.rest
CaltexBevo
CaltexBevoCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Drive a headless browser to navigate, interact, and verify web pages.

Updated Feb 5, 2026
Search Tags:#automation#qa#diff#playwright#headless#screenshot#snapshot
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill gstack-caltexbevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill gstack-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, automated QA testing and browser-based dogfooding by driving a headless browser to navigate pages, interact with UI elements, verify state, and capture bug evidence with diffs and annotated screenshots.

Core Features & Use Cases

  • Persistent headless browsing for automated QA, staging verification, and bug reproduction.
  • Snapshot accessibility trees, diff changes, annotate screenshots, and test responsive layouts.
  • Verify forms, dialogs, uploads, cookies, and dynamic content with reproducible evidence for bug reports.
  • Integrates into CI/CD workflows to validate builds and deployments with real browser interactions.

Quick Start

Invoke the browse skill to start the headless browser, then use commands like goto, snapshot, click, and screenshot to test a page.

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 in a headless browser?▼

Headless browser QA automation drives a browser to navigate pages, interact with UI elements, and verify state. It captures diffs and annotated screenshots to provide reproducible evidence for bug reports.

Can I test responsive layouts and capture annotated screenshots during web automation?▼

Yes, you can test responsive layouts and capture annotated screenshots during web automation. The headless browser snapshots accessibility trees, diffs changes, and marks visual evidence for bug reproduction.

Does headless browser automation support handling cookies, forms, and file uploads?▼

Headless browser automation supports handling cookies, forms, and file uploads. It verifies dynamic content and dialogs by importing cookies and driving form submissions with reproducible results.

What is the best way to integrate headless browser QA into CI/CD workflows?▼

Integrating headless browser QA into CI/CD workflows validates builds through real browser interactions. It navigates staging environments, verifies deployments, and returns concise results with diffing evidence.

Why use snapshot diffing for automated web testing instead of manual verification?▼

Snapshot diffing for automated web testing catches visual and accessibility tree changes that manual verification misses. It provides reproducible, annotated screenshots that serve as concrete evidence for bug reports.

Do I need Playwright installed to run headless browser automation for QA?▼

Playwright is a keyword associated with this headless browser automation approach, but the skill operates independently without external dependencies. It handles navigation, clicking, and screenshotting internally.

Related Skills

Explore More Software Engineering Skills→
limzivectorlimzivector

setup-browser-cookies

Import browser cookies into Playwright headless browser sessions.

Community
Intermediate
2460124601

browse

Automate QA testing by controlling a persistent headless Chromium instance.

Community
Advanced
ajstack22ajstack22

atlas-agent-devops

Automate deployment, CI/CD orchestration, and infrastructure management across environments.

Community
Intermediate
chad3814chad3814

Backend API

Build Express API endpoints with typed validation and SSE progress streaming.

Community
Advanced