skills.rest
wodeh
wodehCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate QA testing with a headless Chromium browser and YAML-defined workflows.

Updated May 11, 2026
Search Tags:#automation#testing#qa#playwright#browser#headless
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-wodeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/wodeh/gstack-kimi/tree/main
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, puppeteer-core, and includes scripts (resource) components.

What problem does it solve?

The rapid, repeatable QA testing workflow required to verify deployments, catch regressions, and collect bug evidence across sites is often manual and error-prone. GStack provides a fast headless browser and a set of deterministic browser-skills to automate interactions, assertions, and visual proofs.

Core Features & Use Cases

  • End-to-end QA testing with a persistent headless Chromium daemon and 70+ commands for navigation, interaction, and validation.
  • Deterministic browser-skill execution that can be codified into scripts for repeatable tests across pages, forms, and responsive layouts.
  • Bug capture with annotated screenshots, diffs, and logs to streamline debugging and handoff.

Quick Start

Open a URL with the built-in browser, interact with elements, and verify the expected results.

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

Automate QA testing by orchestrating a persistent headless Chromium daemon with structured, repeatable workflows to navigate pages, interact with elements, and validate expected results across deployments.

Can I capture bug evidence like annotated screenshots during Playwright testing?▼

Capture bug evidence during Playwright testing by generating annotated screenshots, diffs, and logs from deterministic browser-skill execution, streamlining debugging and handoff for real-world sites.

How do I run repeatable browser automation scripts across responsive layouts?▼

Run repeatable browser automation scripts across responsive layouts by codifying deterministic interactions into workflows that validate forms, dialogs, and page states using 70+ built-in commands.

Does this QA automation tool require a specific configuration format to start?▼

This QA automation tool requires a YAML frontmatter defining at least a name and description to initialize, supporting optional scripts, references, and assets loaded on demand while enforcing safety.

What is the best way to validate site dogfooding without manual interaction?▼

Validate site dogfooding without manual interaction by applying deterministic headless browser workflows that execute automated navigation, assertions, and visual proofs across real-world site pages.

Playwright vs Puppeteer for headless browser QA testing workflows?▼

Playwright and Puppeteer integrate within this headless browser QA testing workflow, combining a persistent Chromium daemon with deterministic browser-skill execution to produce repeatable validation results.

Related Skills

Explore More Software Engineering Skills→
vuminhieuvuminhieu

chrome-devtools

Orchestrate Puppeteer scripts with persistent sessions for browser automation and testing.

Community
Advanced
lendtrainlendtrain
4

browse

Automate QA workflows with a programmable headless browser.

Community
Advanced
apeejay-educationapeejay-education

browse

Operate a persistent headless Chromium browser for QA testing and site dogfooding.

Official
Advanced
SakshamKandelSakshamKandel

gstack

Automate QA testing with a persistent Playwright-based headless browser.

Community
Advanced