gstack

Provides structured AI agent workflow skills and a persistent headless Chromium browser for software development.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill gstack-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill gstack-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? AI coding agents lack structured engineering workflows and fast, stateful browser access, causing slow browser automation, lost login sessions, and inconsistent review, QA, and release processes. ## Core Features & Use Cases - Workflow skill collection: Over 20 specialist skills covering CEO-level plan review, engineering review, design consultation, PR review, debugging, QA, shipping, documentation, and retrospectives. - Persistent headless browser: A compiled CLI talks to a long-lived Chromium daemon over localhost HTTP, delivering ~100ms commands after the first call, with ref-based element selection via the accessibility tree. - Authenticated testing and handoff: Import cookies from real browsers, save and restore sessions, and hand off to a visible Chrome window when CAPTCHAs or MFA block automation. - Use Case: Run /qa to open a real browser against your staging app, find bugs, fix them, and re-verify, then run /ship to test, review, push, and open a PR in one command. ## Quick Start Ask the agent to run the /office-hours skill to reframe your product idea, then use /qa to test your app in a real browser.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate browser testing with an AI coding agent?

Use the /browse skill or the $B CLI to control a persistent headless Chromium daemon. Run snapshot -i to get @e refs for page elements, then click, fill, and navigate with ~100ms per command after the first call.

What workflow skills does gstack include for code review and shipping?

It includes /review for pre-landing PR review, /qa and /qa-only for browser-based testing, /ship for test-review-push-PR in one command, /plan-ceo-review and /plan-eng-review for planning, and /debug for root-cause investigation.

Can I test authenticated pages with a headless browser?

Yes. The /setup-browser-cookies skill imports cookies from your real Chrome, Arc, Brave, or Edge by decrypting the Chromium cookie database with macOS Keychain approval. Sessions persist across commands in the daemon.

Why use a CLI instead of MCP for browser automation?

MCP adds JSON schema overhead of 1500-2000 tokens per call and fragile persistent connections. The gstack CLI outputs plain text with zero context overhead and achieves ~100-200ms per command via a persistent daemon.

What are the limitations of gstack cookie import?

Cookie decryption is only supported on macOS via Keychain; Linux and Windows credential stores are not implemented. Cookie values are never written to disk in plaintext and the browser database is opened read-only.