Suits founders, tech leads and first-time Claude Code users who are comfortable with git and a terminal; you need Claude Code and Bun installed first.

What can you build with gstack?

Pressure-test a product idea with /office-hours and /plan-ceo-review before writing code. Review a branch for production bugs with /review. Run /qa against a staging URL to test it in a real browser. Audit a repo for security issues with /cso. Roll out a shared set of AI workflows to a whole team through team mode.

How do I get started with gstack?

Install Claude Code, Git and Bun, then run the clone and setup command. Open Claude Code and try /office-hours, then /review on a branch with changes. Commands from the README: git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup.

garrytan /

gstack

Slash-command skills that give Claude Code roles like reviewer, QA and release engineer

137.3k stars
2.6k stars since 3 Oct
TypeScript
Updated today
Some experience
Agent skills & plugins

Open on GitHub (opens in a new tab)

gstack is Garry Tan's personal Claude Code setup, shared as open source. Instead of typing free-form prompts, you call a slash command such as /office-hours, /plan-ceo-review, /review, /qa or /ship. Each one puts the agent into a defined role with its own process.

The skills are Markdown files installed into ~/.claude/skills. A setup script also builds a bundled browser so QA and browsing skills can open real pages. A team mode lets a repo ask teammates to install gstack and keep it updated.

It is not limited to Claude Code. The README lists experimental installs for Codex CLI, OpenCode, Cursor, Copilot CLI and others, plus a short digest for any agent that reads rules files. Safety commands like /careful and /freeze are enforced only on Claude Code; elsewhere they advise.

What it does

Role-based slash commands
The README describes 23 specialists and 8 power tools covering product review, engineering planning, design review, code review, QA, security and release.
Real-browser QA
/qa works against a staging URL or an isolated local API, CLI, job or webhook. Setup builds a bundled browser, or uses the Aside browser on macOS if present.
Security audit
/cso runs OWASP and STRIDE audits. It needs a recent Bun and a native toolchain, and reports 'not assessed' if they are missing.
Team mode
One command bootstraps a repo so teammates get gstack automatically, with a throttled update check. You can make it required or optional.
Works with other agents
A --host flag installs for Codex, OpenCode, Cursor, Copilot CLI and more, with tiers from full to instruction-only.

What you could build

Pressure-test a product idea with /office-hours and /plan-ceo-review before writing code.
Review a branch for production bugs with /review.
Run /qa against a staging URL to test it in a real browser.
Audit a repo for security issues with /cso.
Roll out a shared set of AI workflows to a whole team through team mode.

Get started

Install Claude Code, Git and Bun, then run the clone and setup command. Open Claude Code and try /office-hours, then /review on a branch with changes.

git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup

Commands are copied from the project's README. Read it on GitHub for the full setup.

Anything better than gstack?

gstack is a strong pick for role-based Claude Code workflows (planning, QA, security, release) with real-browser QA. Look elsewhere if you want a lifecycle-oriented skill pack or a bigger bundled setup with hooks and memory.