gstack
CLI Toolgarrytan/gstack
Opinionated tools that turn Claude Code into a virtual engineering team.
Overview
A set of 23 curated slash commands that give Claude Code specialized roles such as CEO, Designer, QA, and Release Engineer. Helps solo developers ship faster by structuring AI-assisted workflows.
README Preview
# gstack\n\n> "I don't think I've typed like a line of code probably since December, basically, which is an extremely large change." — [Andrej Karpathy](https://fortune.com/2026/03/21/andrej-karpathy-openai-cofounder-ai-agents-coding-state-of-psychosis-openclaw/), No Priors podcast, March 2026\n\nWhen I heard Karpathy say this, I wanted to find out how. How does one person ship like a team of twenty? Peter Steinberger built [OpenClaw](https://github.com/openclaw/openclaw) — 247K GitHub stars — essentially solo with AI agents. The revolution is here. A single builder with the right tooling can move faster than a traditional team.\n\nI'm [Garry Tan](https://x.com/garrytan), President & CEO of [Y Combinator](https://www.ycombinator.com/). I've worked with thousands of startups — Coinbase, Instacart, Rippling — when they were one or two people in a garage. Before YC, I was one of the first eng/PM/designers at Palantir, cofounded Posterous (sold to Twitter), and built Bookface, YC's internal social network.\n\n**gstack is my answer.** I've been building products for twenty years, and right now I'm shipping more products than I ever have. In the last 60 days: 3 production services, 40+ shipped features, part-time, while running YC full-time. On logical code change — not raw LOC, which AI inflates — my 2026 run rate is **~810× my 2013 pace** (11,417 vs 14 logical lines/day). Year-to-date (through April 18), 2026 has already produced **240× the entire 2013 year**. Measured across 40 public + private `garrytan/*` repos including Bookface, after excluding one demo repo. AI wrote most of it. The point isn't who typed it, it's what shipped.\n\n> The LOC critics aren't wrong that raw line counts inflate with AI. They are wrong that normalized-for-inflation, I'm less productive. I'm more productive, by a lot. Full methodology, caveats, and reproduction script: **[On the LOC Controversy](docs/ON_THE_LOC_CONTROVERSY.md)**.\n\n**2026 — 1,237 contributions and counting:**\n\n\n\n**20
FAQ (5)
TroubleshootingHow to prevent /review and /ship from showing false deletions when origin/<base> is ahead of my feature branch?
This occurs because the diff uses a two-dot comparison git diff origin/<base>, which shows commits on the base branch not yet in your branch as deletions. The permanent fix is to use git diff $(git merge-base origin/<base> HEAD), which diffs your working tree against the merge-base, excluding base-only commits while still including uncommitted changes. This was merged in PR #1594. As a temporary workaround, run git merge origin/<base> before /review to avoid false deletions.
TroubleshootingWhy do CJK characters appear garbled (e.g., 管理工具 becomes 3用箱) in gstack AskUserQuestion, and how can I fix it?
This bug was caused by the model escaping CJK characters with \\uXXXX in AskUserQuestion JSON, leading to incorrect codepoints. The fix: Edit scripts/resolvers/preamble/generate-ask-user-format.ts to add rule 12 forbidding \\uXXXX escaping for non-ASCII characters, then run bun run gen:skill-docs --host all. Alternatively, update to the latest gstack version where this is resolved. The root cause was the model’s default escaping behavior for long, multi-line question strings common in plan-review skills.
TroubleshootingWhy does Codex review fail with 'error: the argument \\'[PROMPT]\\' cannot be used with \\'--base <BRANCH>\\' after upgrading Codex CLI?
This occurs with Codex CLI ≥ 0.124.0-alpha.2, which no longer allows the --base flag when a prompt is provided. Workaround: edit ~/.claude/skills/gstack-codex/SKILL.md (or team-mode path) and remove the --base <base> argument from both codex review invocations in Step 2A. Then add a git diff instruction to the prompt, e.g., 'Review the changes on this branch against the base branch <base>. Run git diff <base>...HEAD to see the diff.' Alternatively, downgrade Codex CLI to a version before 0.124.x. The upstream fix is tracked in this issue.
TroubleshootingWhat are the security risks of using gstack and how can I mitigate them?
When installing gstack, key risks include supply-chain attacks (clone only from the official repo and verify commits), over-powered agent workflows (use read-only skills like qa-only, enable /careful), local daemon token exposure (stop the browse daemon when idle), cookie import dangers (use a dedicated browser profile), prompt injection from malicious websites (keep GSTACK_SECURITY_OFF=0), telemetry leakage (run 'gstack-config set telemetry off'), and oversized ML downloads. Mitigations: audit code before running, limit skill scopes, restrict token access, disable sync unless trusted, and never expose API keys. For full details, see the repo's security documentation.
TroubleshootingWhy does running './setup --help' start the installation instead of showing help?
This was a known bug where unrecognized flags like --help caused the setup script to proceed with installation. It has been fixed in a later update. Upgrade to the latest version of the software to get correct --help behavior. If you cannot upgrade, avoid using --help and refer to the project documentation directly.