"I don't think I've typed like a line of code probably since December, basically, which is an extremely large change." — Andrej Karpathy, No Priors podcast, March 2026

When 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 — 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.

I'm Garry Tan, President & CEO of Y Combinator. 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.

gstack is my answer. I've been building products for twenty years, and right now I'm shipping more code than I ever have. In the last 60 days: 600,000+ lines of production code (35% tests), 10,000-20,000 lines per day, part-time, while running YC full-time. Here's my last /retro across 3 projects: 140,751 lines added, 362 commits, ~115k net LOC in one week.

2026 — 1,237 contributions and counting:

2013 — when I built Bookface at YC (772 contributions):

Same person. Different era. The difference is the tooling.

gstack is how I do it. It turns Claude Code into a virtual engineering team — a CEO who rethinks the product, an eng manager who locks architecture, a designer who catches AI slop, a reviewer who finds production bugs, a QA lead who opens a real browser, a security officer who runs OWASP + STRIDE audits, and a release engineer who ships the PR. Twenty specialists and eight power tools, all slash commands, all Markdown, all free, MIT license.

This is my open source software factory. I use it every day. I'm sharing it because these tools should be available to everyone.

Fork it. Improve it. Make it yours. And if you want to hate on free open source software — you're welcome to, but I'd rather you just try it first.

Who this is for:

• Founders and CEOs — especially technical ones who still want to ship
• First-time Claude Code users — structured roles instead of a blank prompt
• Tech leads and staff engineers — rigorous review, QA, and release automation on every PR

1. Install gstack (30 seconds — see below)
2. Run /office-hours — describe what you're building
3. Run /plan-ceo-review on any feature idea
4. Run /review on any branch with changes
5. Run /qa on your staging URL
6. Stop there. You'll know if this is for you.

Requirements: Claude Code, Git, Bun v1.0+, Node.js (Windows only)

Open Claude Code and paste this. Claude does the rest.

Install gstack: run git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup then add a "gstack" section to CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp__claude-in-chrome__* tools, and lists the available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /design-shotgun, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /connect-chrome, /qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /retro, /investigate, /document-release, /codex, /cso, /autoplan, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade. Then ask the user if they also want to add gstack to the current project so teammates get it.

Add gstack to this project: run cp -Rf ~/.claude/skills/gstack .claude/skills/gstack && rm -rf .claude/skills/gstack/.git && cd .claude/skills/gstack && ./setup then add a "gstack" section to this project's CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp__claude-in-chrome__* tools, lists the available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /retro, /investigate, /document-release, /codex, /cso, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade, and tells Claude that if gstack skills aren't working, run cd .claude/skills/gstack && ./setup to build the binary and register skills.

Real files get committed to your repo (not a submodule), so git clone just works. Everything lives inside .claude/. Nothing touches your PATH or runs in the background.

Contributing or need full history? The commands above use --depth 1 for a fast install. If you plan to contribute or need full git history, do a full clone instead:

git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack

gstack works on any agent that supports the SKILL.md standard. Skills live in .agents/skills/ and are discovered automatically.

Install to one repo:

git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git .agents/skills/gstack
cd .agents/skills/gstack && ./setup --host codex

When setup runs from .agents/skills/gstack, it installs the generated Codex skills next to it in the same repo and does not write to ~/.codex/skills.

Install once for your user account:

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

setup --host codex creates the runtime root at ~/.codex/skills/gstack and links the generated Codex skills at the top level. This avoids duplicate skill discovery from the source repo checkout.

Or let setup auto-detect which agents you have installed:

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

For Codex-compatible hosts, setup now supports both repo-local installs from .agents/skills/gstack and user-global installs from ~/.codex/skills/gstack. All 29 skills work across all supported agents. Hook-based safety skills (careful, freeze, guard) use inline safety advisory prose on non-Claude hosts.

gstack works with Factory Droid. Skills install to .factory/skills/ and are discovered automatically. Sensitive skills (ship, land-and-deploy, guard) use disable-model-invocation: true so Droids don't auto-invoke them.

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

Skills install to ~/.factory/skills/gstack-*/. Restart droid to rescan skills, then type /qa to get started.

You:    I want to build a daily briefing app for my calendar.
You:    /office-hours
Claude: [asks about the pain — specific examples, not hypotheticals]

You:    Multiple Google calendars, events with stale info, wrong locations.
        Prep takes forever and the results aren't good enough...

Claude: I'm going to push back on the framing. You said "daily briefing
        app." But what you actually described is a personal chief of
        staff AI.
        [extracts 5 capabilities you didn't realize you were describing]
        [challenges 4 premises — you agree, disagree, or adjust]
        [generates 3 implementation approaches with effort estimates]
        RECOMMENDATION: Ship the narrowest wedge tomorrow, learn from
        real usage. The full vision is a 3-month project — start with
        the daily briefing that actually works.
        [writes design doc → feeds into downstream skills automatically]

You:    /plan-ceo-review
        [reads the design doc, challenges scope, runs 10-section review]

You:    /plan-eng-review
        [ASCII diagrams for data flow, state machines, error paths]
        [test matrix, failure modes, security concerns]

You:    Approve plan. Exit plan mode.
        [writes 2,400 lines across 11 files. ~8 minutes.]

You:    /review
        [AUTO-FIXED] 2 issues. [ASK] Race condition → you approve fix.

You:    /qa https://staging.myapp.com
        [opens real browser, clicks through flows, finds and fixes a bug]

You:    /ship
        Tests: 42 → 51 (+9 new). PR: github.com/you/app/pull/42

You said "daily briefing app." The agent said "you're building a chief of staff AI" — because it listened to your pain, not your feature request. Eight commands, end to end. That is not a copilot. That is a team.

gstack is a process, not a collection of tools. The skills run in the order a sprint runs:

Think → Plan → Build → Review → Test → Ship → Reflect

Each skill feeds into the next. /office-hours writes a design doc that /plan-ceo-review reads. /plan-eng-review writes a test plan that /qa picks up. /review catches bugs that /ship verifies are fixed. Nothing falls through the cracks because every step knows what came before it.

Deep dives with examples and philosophy for every skill →

gstack works well with one sprint. It gets interesting with ten running at once.

Design is at the heart. /design-consultation doesn't just pick fonts. It researches what's out there in your space, proposes safe choices AND creative risks, generates realistic mockups of your actual product, and writes DESIGN.md — and then /design-review and /plan-eng-review read what you chose. Design decisions flow through the whole system.

/qa was a massive unlock. It let me go from 6 to 12 parallel workers. Claude Code saying "I SEE THE ISSUE" and then actually fixing it, generating a regression test, and verifying the fix — that changed how I work. The agent has eyes now.

Smart review routing. Just like at a well-run startup: CEO doesn't have to look at infra bug fixes, design review isn't needed for backend changes. gstack tracks what reviews are run, figures out what's appropriate, and just does the smart thing. The Review Readiness Dashboard tells you where you stand before you ship.

Test everything. /ship bootstraps test frameworks from scratch if your project doesn't have one. Every /ship run produces a coverage audit. Every /qa bug fix generates a regression test. 100% test coverage is the goal — tests make vibe coding safe instead of yolo coding.

/document-release is the engineer you never had. It reads every doc file in your project, cross-references the diff, and updates everything that drifted. README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, TODOS — all kept current automatically. And now /ship auto-invokes it — docs stay current without an extra command.

Real browser mode. $B connect launches your actual Chrome as a headed window controlled by Playwright. You watch Claude click, fill, and navigate in real time — same window, same screen. A subtle green shimmer at the top edge tells you which Chrome window gstack controls. All existing browse commands work unchanged. $B disconnect returns to headless. A Chrome extension Side Panel shows a live activity feed of every command and a chat sidebar where you can direct Claude. This is co-presence — Claude isn't remote-controlling a hidden browser, it's sitting next to you in the same cockpit.

Sidebar agent — your AI browser assistant. Type natural language instructions in the Chrome side panel and a child Claude instance executes them. "Navigate to the settings page and screenshot it." "Fill out this form with test data." "Go through every item in this list and extract the prices." Each task gets up to 5 minutes. The sidebar agent runs in an isolated session, so it won't interfere with your main Claude Code window. It's like having a second pair of hands in the browser.

Personal automation. The sidebar agent isn't just for dev workflows. Example: "Browse my kid's school parent portal and add all the other parents' names, phone numbers, and photos to my Google Contacts." Two ways to get authenticated: (1) log in once in the headed browser — your session persists, or (2) run /setup-browser-cookies to import cookies from your real Chrome. Once authenticated, Claude navigates the directory, extracts the data, and creates the contacts.

Browser handoff when the AI gets stuck. Hit a CAPTCHA, auth wall, or MFA prompt? $B handoff opens a visible Chrome at the exact same page with all your cookies and tabs intact. Solve the problem, tell Claude you're done, $B resume picks up right where it left off. The agent even suggests it automatically after 3 consecutive failures.

Multi-AI second opinion. /codex gets an independent review from OpenAI's Codex CLI — a completely different AI looking at the same diff. Three modes: code review with a pass/fail gate, adversarial challenge that actively tries to break your code, and open consultation with session continuity. When both /review (Claude) and /codex (OpenAI) have reviewed the same branch, you get a cross-model analysis showing which findings overlap and which are unique to each.

Safety guardrails on demand. Say "be careful" and /careful warns before any destructive command — rm -rf, DROP TABLE, force-push, git reset --hard. /freeze locks edits to one directory while debugging so Claude can't accidentally "fix" unrelated code. /guard activates both. /investigate auto-freezes to the module being investigated.

Proactive skill suggestions. gstack notices what stage you're in — brainstorming, reviewing, debugging, testing — and suggests the right skill. Don't like it? Say "stop suggesting" and it remembers across sessions.

gstack is powerful with one sprint. It is transformative with ten running at once.

Conductor runs multiple Claude Code sessions in parallel — each in its own isolated workspace. One session running /office-hours on a new idea, another doing /review on a PR, a third implementing a feature, a fourth running /qa on staging, and six more on other branches. All at the same time. I regularly run 10-15 parallel sprints — that's the practical max right now.

The sprint structure is what makes parallelism work. Without a process, ten agents is ten sources of chaos. With a process — think, plan, build, review, test, ship — each agent knows exactly what to do and when to stop. You manage them the way a CEO manages a team: check in on the decisions that matter, let the rest run.

Free, MIT licensed, open source. No premium tier, no waitlist.

I open sourced how I build software. You can fork it and make it your own.

We're hiring. Want to ship 10K+ LOC/day and help harden gstack? Come work at YC — ycombinator.com/software Extremely competitive salary and equity. San Francisco, Dogpatch District.

gstack includes opt-in usage telemetry to help improve the project. Here's exactly what happens:

• Default is off. Nothing is sent anywhere unless you explicitly say yes.
• On first run, gstack asks if you want to share anonymous usage data. You can say no.
• What's sent (if you opt in): skill name, duration, success/fail, gstack version, OS. That's it.
• What's never sent: code, file paths, repo names, branch names, prompts, or any user-generated content.
• Change anytime: gstack-config set telemetry off disables everything instantly.

Data is stored in Supabase (open source Firebase alternative). The schema is in supabase/migrations/ — you can verify exactly what's collected. The Supabase publishable key in the repo is a public key (like a Firebase API key) — row-level security policies deny all direct access. Telemetry flows through validated edge functions that enforce schema checks, event type allowlists, and field length limits.

Local analytics are always available. Run gstack-analytics to see your personal usage dashboard from the local JSONL file — no remote data needed.

Skill not showing up? cd ~/.claude/skills/gstack && ./setup

/browse fails? cd ~/.claude/skills/gstack && bun install && bun run build

Stale install? Run /gstack-upgrade — or set auto_upgrade: true in ~/.gstack/config.yaml

Want shorter commands? cd ~/.claude/skills/gstack && ./setup --no-prefix — switches from /gstack-qa to /qa. Your choice is remembered for future upgrades.

Want namespaced commands? cd ~/.claude/skills/gstack && ./setup --prefix — switches from /qa to /gstack-qa. Useful if you run other skill packs alongside gstack.

Codex says "Skipped loading skill(s) due to invalid SKILL.md"? Your Codex skill descriptions are stale. Fix: cd ~/.codex/skills/gstack && git pull && ./setup --host codex — or for repo-local installs: cd "$(readlink -f .agents/skills/gstack)" && git pull && ./setup --host codex

Windows users: gstack works on Windows 11 via Git Bash or WSL. Node.js is required in addition to Bun — Bun has a known bug with Playwright's pipe transport on Windows (bun#4253). The browse server automatically falls back to Node.js. Make sure both bun and node are on your PATH.

Claude says it can't see the skills? Make sure your project's CLAUDE.md has a gstack section. Add this:

## gstack
Use /browse from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.
Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review,
/design-consultation, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse,
/qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /retro,
/investigate, /document-release, /codex, /cso, /autoplan, /careful, /freeze, /guard,
/unfreeze, /gstack-upgrade.

MIT. Free forever. Go build something.

「我大概從十二月開始就沒有打過一行程式碼了，這是一個非常巨大的轉變。」— Andrej Karpathy，No Priors podcast，2026 年 3 月

當我聽到 Karpathy 這麼說時，我想知道他是怎麼做到的。一個人怎麼能像二十人團隊一樣高速交付？Peter Steinberger 打造了 OpenClaw — 247K GitHub 星標 — 基本上是靠 AI agent 獨自完成的。革命已經到來。一個擁有正確工具的建造者，可以比傳統團隊更快地行動。

我是 Garry Tan，Y Combinator 的總裁兼執行長。我與數千家新創公司合作過 — Coinbase、Instacart、Rippling — 在它們還只是車庫裡一兩個人的時候。在 YC 之前，我是 Palantir 最早的工程師/PM/設計師之一，共同創辦了 Posterous（後被 Twitter 收購），並打造了 Bookface，YC 的內部社群網路。

gstack 是我的答案。 我做產品已經二十年了，而現在我寫的程式碼比以往任何時候都多。過去 60 天：600,000+ 行正式程式碼（35% 為測試），每天 10,000-20,000 行，兼職進行，同時全職經營 YC。以下是我最近一次橫跨 3 個專案的 /retro：140,751 行新增，362 次 commit，約 115k 淨 LOC，僅一週。

2026 — 1,237 次貢獻，持續增加中：

2013 — 我在 YC 打造 Bookface 時（772 次貢獻）：

同一個人。不同的時代。差異在於工具。

gstack 就是我的做法。 它把 Claude Code 變成一個虛擬工程團隊 — 一位重新思考產品的 CEO、一位鎖定架構的工程經理、一位抓出 AI 粗製濫造的設計師、一位找出正式環境 bug 的審查者、一位打開真實瀏覽器的 QA 主管、一位執行 OWASP + STRIDE 審計的資安長，以及一位推送 PR 的發布工程師。二十位專家和八個強大工具，全部是 slash command，全部是 Markdown，全部免費，MIT 授權。

這是我的開源軟體工廠。我每天都在用。我分享它，因為這些工具應該讓每個人都能使用。

Fork 它。改進它。讓它成為你的。如果你想批評免費開源軟體 — 歡迎，但我更希望你先試試看。

這是為誰準備的：

• 創辦人和 CEO — 特別是仍然想要親自交付程式碼的技術型創辦人
• 第一次使用 Claude Code 的人 — 結構化角色取代空白 prompt
• 技術主管和資深工程師 — 每個 PR 都有嚴謹的審查、QA 和發布自動化

1. 安裝 gstack（30 秒 — 見下方）
2. 執行 /office-hours — 描述你正在打造的東西
3. 對任何功能構想執行 /plan-ceo-review
4. 對任何有變更的分支執行 /review
5. 對你的 staging URL 執行 /qa
6. 到此為止。你會知道這適不適合你。

需求： Claude Code、Git、Bun v1.0+、Node.js（僅 Windows 需要）

打開 Claude Code 並貼上以下內容。Claude 會完成剩下的工作。

安裝 gstack：執行 git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup 然後在 CLAUDE.md 中加入一個「gstack」區段，說明使用 gstack 的 /browse skill 來進行所有網頁瀏覽，永遠不使用 mcp__claude-in-chrome__* 工具，並列出可用的 skill：/office-hours、/plan-ceo-review、/plan-eng-review、/plan-design-review、/design-consultation、/design-shotgun、/review、/ship、/land-and-deploy、/canary、/benchmark、/browse、/connect-chrome、/qa、/qa-only、/design-review、/setup-browser-cookies、/setup-deploy、/retro、/investigate、/document-release、/codex、/cso、/autoplan、/careful、/freeze、/guard、/unfreeze、/gstack-upgrade。然後詢問使用者是否也要將 gstack 加入目前的專案，以便團隊成員也能使用。

將 gstack 加入此專案：執行 cp -Rf ~/.claude/skills/gstack .claude/skills/gstack && rm -rf .claude/skills/gstack/.git && cd .claude/skills/gstack && ./setup 然後在此專案的 CLAUDE.md 中加入一個「gstack」區段，說明使用 gstack 的 /browse skill 來進行所有網頁瀏覽，永遠不使用 mcp__claude-in-chrome__* 工具，列出可用的 skill：/office-hours、/plan-ceo-review、/plan-eng-review、/plan-design-review、/design-consultation、/review、/ship、/land-and-deploy、/canary、/benchmark、/browse、/qa、/qa-only、/design-review、/setup-browser-cookies、/setup-deploy、/retro、/investigate、/document-release、/codex、/cso、/careful、/freeze、/guard、/unfreeze、/gstack-upgrade，並告訴 Claude 如果 gstack skill 無法運作，執行 cd .claude/skills/gstack && ./setup 來建置 binary 並註冊 skill。

真實檔案會被 commit 到你的 repo（不是 submodule），所以 git clone 就能直接使用。所有東西都在 .claude/ 裡。不會動到你的 PATH，也不會在背景執行任何東西。

想要貢獻或需要完整歷史？ 上述指令使用 --depth 1 來快速安裝。如果你計畫貢獻或需要完整的 git 歷史，請改用完整 clone：

git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack

gstack 適用於任何支援 SKILL.md 標準的 agent。Skill 位於 .agents/skills/，會被自動發現。

安裝到單一 repo：

git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git .agents/skills/gstack
cd .agents/skills/gstack && ./setup --host codex

當 setup 從 .agents/skills/gstack 執行時，會將生成的 Codex skill 安裝在同一個 repo 中，不會寫入 ~/.codex/skills。

安裝到使用者帳號（全域）：

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

setup --host codex 會在 ~/.codex/skills/gstack 建立 runtime root，並在頂層連結生成的 Codex skill。這避免了從來源 repo checkout 產生重複的 skill 發現。

或讓 setup 自動偵測你安裝了哪些 agent：

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

對於 Codex 相容的主機，setup 現在同時支援從 .agents/skills/gstack 的 repo 本地安裝和從 ~/.codex/skills/gstack 的使用者全域安裝。所有 28 個 skill 都能在所有支援的 agent 上運作。Hook 型安全 skill（careful、freeze、guard）在非 Claude 主機上使用內嵌安全提示文字。

你：    我想做一個日曆每日簡報 app。
你：    /office-hours
Claude: [詢問痛點 — 具體的例子，不是假設]

你：    多個 Google 日曆、事件資訊過時、地點錯誤。
        準備工作費時且結果不夠好...

Claude: 我要挑戰你的定義。你說的是「每日簡報 app」。
        但你實際描述的是一個個人幕僚長 AI。
        [提取你沒意識到的 5 項能力]
        [挑戰 4 個前提 — 你同意、不同意或調整]
        [生成 3 種實作方案及工時估算]
        建議：明天就發布最窄的切入點，從真實使用中學習。
        完整願景是 3 個月的專案 — 先從一個真正有用的
        每日簡報開始。
        [撰寫設計文件 → 自動傳遞給下游 skill]

你：    /plan-ceo-review
        [讀取設計文件，挑戰範圍，執行 10 個章節的審查]

你：    /plan-eng-review
        [資料流程 ASCII 圖、狀態機、錯誤處理路徑]
        [測試矩陣、失敗模式、安全疑慮]

你：    批准計畫。退出 plan mode。
        [在 11 個檔案中寫了 2,400 行。約 8 分鐘。]

你：    /review
        [自動修復] 2 個問題。[詢問] Race condition → 你批准修復。

你：    /qa https://staging.myapp.com
        [打開真實瀏覽器，點擊各個流程，找到並修復一個 bug]

你：    /ship
        測試：42 → 51（+9 新增）。PR: github.com/you/app/pull/42

你說的是「每日簡報 app」。Agent 說「你正在打造一個幕僚長 AI」 — 因為它聽的是你的痛點，而不是你的功能需求。八個指令，端到端。這不是副駕駛。這是一個團隊。

gstack 是一個流程，不是工具的集合。Skill 按照衝刺的順序執行：

思考 → 規劃 → 建造 → 審查 → 測試 → 發布 → 回顧

每個 skill 都銜接下一個。/office-hours 撰寫的設計文件會被 /plan-ceo-review 讀取。/plan-eng-review 撰寫的測試計畫會被 /qa 接手。/review 發現的 bug 會被 /ship 確認已修復。不會有任何東西漏掉，因為每個步驟都知道之前發生了什麼。

每個 skill 的深入說明、範例和設計理念 →

gstack 用一個衝刺就很強大。十個同時執行時更令人驚豔。

設計是核心。 /design-consultation 不只是挑字體。它研究你領域中的現有方案，提出安全選擇和創意風險，生成你實際產品的逼真 mockup，並撰寫 DESIGN.md — 然後 /design-review 和 /plan-eng-review 會讀取你的選擇。設計決策貫穿整個系統。

/qa 是一個巨大的突破。 它讓我從 6 個平行 worker 增加到 12 個。Claude Code 說*「我看到問題了」*然後真的修復它、生成迴歸測試、並驗證修復 — 這改變了我的工作方式。Agent 現在有眼睛了。

智慧審查路由。 就像運作良好的新創公司：CEO 不需要看基礎設施的 bug 修復，設計審查不需要看後端變更。gstack 追蹤哪些審查已執行，判斷什麼是適當的，然後做正確的事。Review Readiness Dashboard 在你發布前告訴你目前的狀態。

測試一切。 /ship 會在你的專案沒有測試框架時從零建立一個。每次 /ship 執行都會產出覆蓋率審計。每個 /qa bug 修復都會生成迴歸測試。100% 測試覆蓋率是目標 — 測試讓 vibe coding 變得安全而非 yolo coding。

/document-release 是你從未有過的工程師。 它讀取你專案中的每個文件檔案，交叉比對 diff，並更新所有偏離的內容。README、ARCHITECTURE、CONTRIBUTING、CLAUDE.md、TODOS — 全部自動保持最新。而且現在 /ship 會自動調用它 — 文件無需額外指令就能保持最新。

真實瀏覽器模式。 $B connect 啟動你實際的 Chrome 作為由 Playwright 控制的 headed 視窗。你即時觀看 Claude 點擊、填寫和導航 — 同一個視窗、同一個螢幕。頂部邊緣的細微綠色微光告訴你 gstack 控制的是哪個 Chrome 視窗。所有現有的 browse 指令都不變。$B disconnect 回到 headless。Chrome 擴充功能 Side Panel 顯示每個指令的即時動態和一個聊天側邊欄，你可以在那裡指揮 Claude。這是共存 — Claude 不是在遠端控制一個隱藏的瀏覽器，它與你坐在同一個駕駛艙。

側邊欄 agent — 你的 AI 瀏覽器助手。 在 Chrome side panel 輸入自然語言指令，一個子 Claude 實例會執行它們。「導航到設定頁面並截圖。」「用測試資料填寫這個表單。」「瀏覽這個列表中的每個項目並提取價格。」每個任務最多 5 分鐘。側邊欄 agent 在隔離的 session 中執行，不會干擾你的主要 Claude Code 視窗。就像在瀏覽器中有第二雙手。

個人自動化。 側邊欄 agent 不只是用於開發工作流程。例如：「瀏覽我小孩學校的家長入口網站，把所有其他家長的姓名、電話號碼和照片加入我的 Google 聯絡人。」兩種認證方式：（1）在 headed 瀏覽器中登入一次 — 你的 session 會保留，或（2）執行 /setup-browser-cookies 從你真實的 Chrome 匯入 cookies。認證後，Claude 導航目錄、提取資料、建立聯絡人。

AI 卡住時的瀏覽器接手。 遇到 CAPTCHA、認證牆或 MFA 提示？$B handoff 打開一個可見的 Chrome，保留你所有的 cookies 和分頁。解決問題，告訴 Claude 你完成了，$B resume 從中斷處繼續。Agent 在連續 3 次失敗後甚至會自動建議此功能。

多 AI 第二意見。 /codex 從 OpenAI 的 Codex CLI 取得獨立審查 — 一個完全不同的 AI 看同一個 diff。三種模式：帶通過/不通過門檻的程式碼審查、主動嘗試破壞你程式碼的對抗性挑戰、以及具有 session 連續性的開放諮詢。當 /review（Claude）和 /codex（OpenAI）都審查了同一個分支，你會得到跨模型分析，顯示哪些發現重疊、哪些是各自獨有的。

按需安全護欄。 說「be careful」，/careful 會在任何破壞性指令前發出警告 — rm -rf、DROP TABLE、force-push、git reset --hard。/freeze 在除錯時將編輯鎖定在一個目錄，防止 Claude 意外「修復」不相關的程式碼。/guard 同時啟用兩者。/investigate 會自動凍結到正在調查的模組。

主動 skill 建議。 gstack 會注意你所處的階段 — 腦力激盪、審查、除錯、測試 — 並建議合適的 skill。不喜歡？說「stop suggesting」，它會跨 session 記住。

gstack 用一個衝刺就很強大。十個同時執行時是變革性的。

Conductor 平行執行多個 Claude Code session — 每個都在自己的隔離工作區中。一個 session 在新想法上執行 /office-hours，另一個在 PR 上做 /review，第三個在實作功能，第四個在 staging 上執行 /qa，還有六個在其他分支上。全部同時進行。我通常執行 10-15 個平行衝刺 — 這是目前的實用上限。

衝刺結構是讓平行化可行的關鍵。沒有流程，十個 agent 就是十個混亂來源。有了流程 — 思考、規劃、建造、審查、測試、發布 — 每個 agent 都確切知道該做什麼和何時停止。你像 CEO 管理團隊那樣管理它們：關注重要的決策，讓其餘的自行運轉。

免費，MIT 授權，開源。沒有付費等級，沒有等候名單。

我開源了我建造軟體的方式。你可以 fork 它，讓它成為你自己的。

我們正在招募。 想要每天交付 10K+ LOC 並幫助強化 gstack？ 來 YC 工作 — ycombinator.com/software 極具競爭力的薪資和股權。舊金山，Dogpatch 區。

gstack 包含選擇加入的使用遙測以幫助改進專案。以下是確切的運作方式：

• 預設為關閉。 除非你明確同意，否則不會向任何地方發送任何東西。
• 首次執行時， gstack 會詢問你是否願意分享匿名使用資料。你可以拒絕。
• 發送的內容（如果你選擇加入）： skill 名稱、持續時間、成功/失敗、gstack 版本、作業系統。就這些。
• 永遠不會發送的內容： 程式碼、檔案路徑、repo 名稱、分支名稱、prompt 或任何使用者生成的內容。
• 隨時可更改： gstack-config set telemetry off 立即停用一切。

資料儲存在 Supabase（開源 Firebase 替代方案）。Schema 在 supabase/migrations/ — 你可以驗證確切收集了什麼。Repo 中的 Supabase publishable key 是公開金鑰（如同 Firebase API key） — row-level security 策略拒絕所有直接存取。遙測透過已驗證的 edge function 流轉，這些 function 強制執行 schema 檢查、事件類型允許清單和欄位長度限制。

本地分析始終可用。 執行 gstack-analytics 查看你從本地 JSONL 檔案獲取的個人使用儀表板 — 不需要遠端資料。

Skill 沒有出現？ cd ~/.claude/skills/gstack && ./setup

/browse 失敗？ cd ~/.claude/skills/gstack && bun install && bun run build

安裝過時？ 執行 /gstack-upgrade — 或在 ~/.gstack/config.yaml 中設定 auto_upgrade: true

想要更短的指令？ cd ~/.claude/skills/gstack && ./setup --no-prefix — 從 /gstack-qa 切換為 /qa。你的選擇會在未來升級時被記住。

想要帶命名空間的指令？ cd ~/.claude/skills/gstack && ./setup --prefix — 從 /qa 切換為 /gstack-qa。在你同時使用其他 skill pack 時很有用。

Codex 顯示 "Skipped loading skill(s) due to invalid SKILL.md"？ 你的 Codex skill 描述過時了。修復方式：cd ~/.codex/skills/gstack && git pull && ./setup --host codex — 或 repo 本地安裝：cd "$(readlink -f .agents/skills/gstack)" && git pull && ./setup --host codex

Windows 使用者： gstack 可在 Windows 11 上透過 Git Bash 或 WSL 運作。除了 Bun 外還需要 Node.js — Bun 在 Windows 上的 Playwright pipe transport 有已知 bug（bun#4253）。Browse server 會自動退回 Node.js。確保 bun 和 node 都在你的 PATH 中。

Claude 說它看不到 skill？ 確保你專案的 CLAUDE.md 有 gstack 區段。加入以下內容：

## gstack
使用 gstack 的 /browse 進行所有網頁瀏覽。永遠不使用 mcp__claude-in-chrome__* 工具。
可用 skill：/office-hours、/plan-ceo-review、/plan-eng-review、/plan-design-review、
/design-consultation、/review、/ship、/land-and-deploy、/canary、/benchmark、/browse、
/qa、/qa-only、/design-review、/setup-browser-cookies、/setup-deploy、/retro、
/investigate、/document-release、/codex、/cso、/autoplan、/careful、/freeze、/guard、
/unfreeze、/gstack-upgrade。

MIT。永遠免費。去打造些什麼吧。