Skip to content

gstack

Markdown skills that give Claude Code and other coding agents roles like CEO, reviewer, QA, and release engine

Stars
139k
Forks
20.6k
Licence
MIT
Language
TypeScript
Last update
4 days ago
Type
Dev tool

What it is

gstack is a set of slash-command skills, written in Markdown with TypeScript tooling, that you install into Claude Code. Each skill gives the agent a specific engineering role, such as product review, architecture lock-in, design critique, code review, browser-based QA, security audit, and shipping a pull request. The README says it is the setup its author, Garry Tan, uses day to day.

  • Run /office-hours to pressure-test a product idea and produce a design doc
  • Run /review on a branch to find bugs that pass CI but may break in production
  • Run /qa against a staging URL to have the agent open a browser, reproduce bugs, and fix them
  • Run /ship to run tests, review, and open a pull request

Great for

  • Developers who already use Claude Code and want structured roles instead of a blank prompt
  • First-time Claude Code users who want guided workflows like /review and /qa
  • Tech leads who want consistent review, QA, and release steps on every pull request
  • Teams willing to add a shared repo hook that requires gstack for AI-assisted work

Not ideal for

  • People who do not use Claude Code or another supported agent, since the skills run inside those harnesses
  • Teams that cannot install Bun 1.3.3 or newer, which setup requires
  • macOS users who want the optional /cso security audit without a native toolchain, since setup leaves /cso unavailable without one
Step-by-step guide: how to use gstackInstall, first run, examples, tips and FAQs

How to get it

  1. 1

    Clone and build from source

    You'll need: Claude Code · Git · Bun v1.4.2+ (setup refuses versions older than 1.3.3) · Node.js (required on Windows and for team-mode hooks)

    Install gstack into Claude Code skills folder

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

    Install for every detected agent (alternative)

    git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack && cd ~/gstack && ./setup --host auto
  2. 2

    Run it

    • Install gstack using the clone and setup command
    • Open Claude Code and run /office-hours and describe what you are building
    • Run /review on any branch that has changes
    • Run /qa on a staging URL or an isolated local service
  3. 3

    Get the most out of it

    • Use /autoplan to review a plan end to end before building
    • Use /ship to run tests, review, and create the PR in one flow
    • Check installed agent versions and tiers with ./setup --status
    • Add team mode with ./setup --team and gstack-team-init so teammates get updates automatically
    • Set gstack-config set update_channel main if you want every merge instead of the stable channel

Downloads

Strengths

  • Free and MIT licensed, with all skills written as Markdown
  • Covers the whole flow from planning to review, QA, and release in one set of commands
  • Supports several coding agents besides Claude Code, with tiers that state how well each is verified

Trade-offs

  • Several parts depend on other tools: Bun 1.3.3 or newer, Node.js on Windows, and a native toolchain for /cso
  • The README's strongest claims about productivity are in a separate document and are the author's own account
  • Non-Claude hosts other than Claude Code are labeled experimental or instruction-only, so they are less tested

Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.