gstack

Automate web QA with a persistent Playwright-based headless browser daemon.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill gstack-kakarottoooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill gstack-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff, and includes scripts (resource) components.

What problem does it solve?

Navigating and validating web pages for QA requires reliable, programmable browser automation. gstack provides a fast, persistent headless browser to run tests, dogfood features, and capture evidence with reproducible results.

Core Features & Use Cases

  • Persistent headless browser: runs a long-lived Chromium daemon to preserve cookies, sessions, and state across commands.
  • QA test toolkit: navigate, click, fill, capture screenshots, diff baseline changes, and verify page states with a rich command set.
  • Bug evidence pipeline: generate annotated screenshots and diffs to help reproduce issues in PRs or reports.
  • Use case: automate login flows, validate checkout sequences, and capture failing states with visual proof.

Quick Start

Start the browse daemon and issue commands like goto, text, snapshot, and screenshot to validate pages quickly.

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?

Automate QA testing using a persistent headless browser daemon to navigate, interact, and verify web pages. It preserves sessions and state across commands, delivering reliable, repeatable results for login or checkout workflows.

What is the best way to capture bug evidence with annotated screenshots?

Capture bug evidence by generating annotated screenshots and diffs during automated browser navigation. This pipeline helps reproduce failing page states and provides visual proof for issue reports or pull requests.

How do I keep browser sessions and cookies persistent across QA commands?

Maintain persistent browser sessions by running a long-lived Chromium daemon. This approach preserves cookies and state across multiple QA commands, ensuring continuous interaction without resetting the session.

Does Playwright support headless browser automation for checkout validation?

Playwright supports headless browser automation for validating checkout sequences. This Skill leverages Playwright to automate interactions and verify page states, delivering reproducible results for e-commerce workflows.

Can I diff baseline page changes during automated web testing?

You can diff baseline page changes during automated web testing using the integrated diffing feature. It compares current page states against baselines to detect visual or structural regressions quickly.

How to start dogfooding web apps with a persistent headless browser?

Start dogfooding web apps by starting the persistent browser daemon and issuing commands like goto, text, snapshot, and screenshot to navigate and validate pages quickly with minimal setup.