Garry Tan's gstack repackaged as a self-contained Claude Code plugin. All 53 gstack skills are vendored inside this plugin, so installing it gives you the skills directly. No external clone, no ./setup step for the core skills.
This is an unofficial wrapper of upstream snapshot 1.52.2.0. gstack is built by Garry Tan and licensed MIT. All credit and ongoing development belong upstream.
/office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /plan-devex-review, /design-consultation, /design-shotgun, /review, /ship, /land-and-deploy, /canary, /benchmark, /retro, /investigate, /document-release, /document-generate, /cso, /autoplan, /devex-review, /careful, /freeze, /guard, /unfreeze, /learn, /spec, /skillify, and more, plus the browser set (/browse, /qa, /scrape, /design-review, /ios-*) covered below.
- All skills live under
skills/<name>/, discovered natively by Claude Code. - gstack's ~66 helper tools are vendored at
bin/andlib/. The skills call them via${CLAUDE_PLUGIN_ROOT}/bin/..., and the tools self-locate, so they run from wherever the plugin is installed. - Runtime state (config, learnings, analytics) lives in
~/.gstack, exactly as upstream. Nothing is written into your repos unless a skill explicitly does so.
- Settings -> Extensions (Plugins) -> Add marketplace, paste:
https://github.com/SMKeramati/gstack - Install gstack.
- Restart Desktop. The skills appear as
/office-hours,/review, etc.
/plugin marketplace add https://github.com/SMKeramati/gstack
/plugin install gstack@gstack
Then start with /office-hours, /review, or /qa <url>.
The browser-driven skills (/browse, /qa, /qa-only, /scrape, /design-review, /design-html, /ios-*, /make-pdf, /setup-browser-cookies, /open-gstack-browser) drive a compiled engine. That binary is too large to ship inside a Git plugin (GitHub's file limit) and also needs a Playwright Chromium at runtime, so it is not vendored.
To enable those skills, run the bundled helper once after install:
/gstack:gstack-build-engine
It compiles the engine from the source vendored here (needs Bun). The first /browse then auto-downloads a Chromium (about 150MB, one time). If you only want the methodology skills (the majority), you can ignore this entirely.
For fully supported browser automation, the upstream native install also remains an option: git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup.
/plugin uninstall gstack@gstack (and optionally rm -rf ~/.gstack to clear state).
gstack is the work of Garry Tan: https://github.com/garrytan/gstack (MIT). This repository only re-lays-out the upstream files as a plugin and rewrites install paths to ${CLAUDE_PLUGIN_ROOT}. It ships no original functionality.