gstack

Automate end-to-end QA testing with a headless browser via Bun and Playwright.

Updated Jun 18, 2026

Search Tags:#automation #testing #debugging #qa #playwright #browser #headless

Ready to run

npx skills add https://github.com/abhishekmmgn/didactic-invention --skill gstack-abhishekmmgn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill gstack-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast, headless browser workflow to QA test and dogfood sites, enabling automated navigation, interaction, and inspection from the command line.

Core Features & Use Cases

Headless QA automation: drive a real browser for testing workflows and capturing evidence (screenshots, logs, HTML/text).
Live debugging and inspection: navigate pages, inspect DOM, take annotated screenshots, and test responsiveness.
Quick-startable end-to-end task: launch, browse, snapshot, and collect artifacts for QA cycles.

Quick Start

Install Bun and build the browser daemon, then run browser commands to drive QA sessions.

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

Automated headless browser QA testing is driven by controlling browser interactions via a local Playwright daemon, executing deterministic navigation and inspection workflows from the command line.

What is the best way to reproduce bugs and capture visual evidence during site testing?▼

Visual bug reproduction and evidence capture during site testing is handled by navigating dynamic content in a headless browser, then automatically collecting screenshots, logs, and HTML artifacts.

Do I need Bun installed to run automated browser testing sessions?▼

Yes, Bun is required as the underlying tooling environment to build the browser daemon and execute the CLI commands that drive headless QA testing sessions.

What kind of artifacts can I collect from automated Playwright navigation workflows?▼

Playwright navigation workflows collect QA artifacts including screenshots, console logs, and extracted HTML or text from pages, forms, and dynamic content during automated testing cycles.

Can I inspect DOM elements and test page responsiveness with headless automation?▼

Yes, you can inspect DOM elements and test page responsiveness by driving a headless browser to navigate pages, inspect the DOM structure, and take annotated screenshots of dynamic content.