gstack

Run QA testing workflows with a persistent headless Chromium browser.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bhianerd/aimemory --skill gstack-bhianerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/bhianerd/aimemory/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/bhianerd/aimemory --skill gstack-bhianerd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

gstack gives you a complete, role-based AI engineering workflow that keeps production-quality rigor across planning, design review, architecture review, QA testing in a real browser, shipping, and follow-through documentation—without you repeating yourself or stitching tools together manually.

Core Features & Use Cases

  • Persistent headless browser QA: Uses a long-lived Chromium daemon to navigate, interact, verify UI state, diff before/after, take annotated evidence screenshots, and validate responsive layouts.
  • Structured end-to-end engineering stages: Suggests and chains adjacent specialist skills by stage (brainstorm → plan → design/eng review → QA → code review → ship → retro), so the workflow stays coherent.
  • Safety and scoped control: Works alongside guard skills like careful/freeze/guard to reduce destructive mistakes and limit edits to a directory during risky tasks.

Quick Start

Invoke gstack for a site check by asking it to verify a user flow on a staging URL and include evidence screenshots of what it tested.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I run headless browser QA testing with Playwright for visual evidence?

Headless browser QA testing with Playwright uses a persistent Chromium daemon to navigate, interact, and capture annotated screenshots as visual evidence. You can verify user flows on staging URLs and validate UI state through snapshot diffs.

Can I perform authenticated testing in a headless browser by importing cookies?

Authenticated testing via cookie import is supported for headless browser workflows. You can import session cookies into the persistent Chromium browser to execute dogfooding workflows and verify protected application areas.

What is diff testing for web automation and when do I need it?

Diff testing for web automation compares before and after UI snapshots to detect unintended visual or state changes. It is needed when verifying responsive layouts, validating form uploads, or handling dialogs during production verification.

Does headless browser QA work for responsive layout audits and dialog handling?

Headless browser QA supports responsive layout audits and dialog handling within web automation workflows. The persistent Chromium browser interacts with elements using ref-based targeting to verify state across different viewport sizes and manage unexpected dialogs.

Do I need a local browse daemon for web automation and visual evidence capture?

A local browse daemon is required for web automation and visual evidence capture. It enables strict local execution with ref-based element targeting, supporting optional safety and scoping controls to limit edits during risky staging checks.