engineering / skill

gstack

Add a set of slash-command skills to Claude Code with commands for product planning, code review, QA, security review and shipping.

Repository owner garrytan

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: Add a set of slash-command skills to Claude Code with commands for product planning, code review, QA, security review and shipping.
Runs in: Local agent with shell, Web service
Operating systems: macOS, Linux, Windows
Needs: Runtime: Git and Bun; Node.js on Windows; Needs internet: Yes; Needs accounts or API keys beyond your agent: Not stated
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type: Skill
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: Claude Code, OpenAI Codex CLI, OpenCode, Cursor, Factory Droid, Kiro, GitHub Copilot CLI and Antigravity CLI as installable hosts, and Slate, OpenClaw, Hermes and GBrain as instruction-only, according to the README. It also describes a short instruction file for any agent that reads a rules file, such as Zed, Amp or Jules.
External costs: The repository is MIT-licensed, and the README says the tools are free. Outside reviews need a signed-in Codex CLI or Claude Code, and the design tools call OpenAI models, for which the README mentions an OPENAI_API_KEY, so provider charges may apply. Your coding agent or model provider may charge for usage.
Permissions: The skills act through your coding agent with the access you give it. According to the README, the install prompt asks Claude to add a gstack section to your CLAUDE.md that tells it to use gstack's /browse skill for web browsing instead of the claude-in-chrome MCP tools, and team mode bootstraps your repo and commits the change. It says browser skills such as /browse and /scrape drive the Aside browser with your real logged-in sessions when it is installed, and otherwise gstack's own bundled browser. /ship syncs main, runs tests, pushes and opens a pull request. /land-and-deploy merges the pull request and checks the deploy. /qa opens a real browser and can fix bugs and commit. /setup-browser-cookies copies cookies you choose from your browsers into gstack's bundled browser. /pair-agent shares that browser with other agents using scoped tokens, and starts an ngrok tunnel for remote agents. The README says safety skills are enforced by hooks only in Claude Code.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

garrytan/gstack

MIT

TypeScript136,157 stars20,209 forksLast pushed 13 Oct 2026 UTC

Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

Skill folders in this repository (63)

Folders that contain a SKILL.md file, from GitHub's file list on 13 Oct 2026 UTC.

View on GitHub ↗

What it does

gstack is a set of slash-command skills for Claude Code, written by Garry Tan. According to the README, it turns Claude Code into a virtual engineering team with specialist roles: a CEO who rethinks the product, an eng manager who locks architecture, a designer, a reviewer, a QA lead who opens a real browser, a security officer and a release engineer. The README counts twenty-three specialists and eight power tools, all as Markdown.

The README says the skills follow a sprint of think, plan, build, review, test, ship and reflect, and that each skill feeds the next. Examples are /office-hours for product questions, /plan-ceo-review, /plan-eng-review and /plan-design-review for plans, /review for code review, /qa for browser and API checks, /cso for security audits, /ship to open a pull request and /land-and-deploy to merge and check production health.

The README also says gstack runs on other agents, with install steps for the OpenAI Codex CLI, OpenCode, Cursor, Factory Droid, Kiro, GitHub Copilot CLI and Antigravity CLI, and a short instruction file for any agent that reads a rules file.

Who it is for

The README names founders and CEOs who still want to ship, first-time Claude Code users, and tech leads and staff engineers.

Example tasks

Run /office-hours to describe what you are building and get pushback on the idea.
Run /plan-eng-review to lock in architecture, data flow, edge cases and tests for a plan.
Run /review on a branch with changes.
Run /qa on a staging URL or an isolated local API, CLI, job or webhook.
Run /ship to sync main, run tests and open a pull request.

Getting started

The README says to paste an install prompt into Claude Code. The prompt clones the repository into the Claude skills folder, runs ./setup, and adds a gstack section to your CLAUDE.md. For shared repositories it gives a team mode that starts with ./setup --team and commits the change to your repo. For other agents it gives ./setup --host auto or ./setup --host codex, and ./setup --status to list installs. The README has the exact commands.

Limitations

gstack is built for Claude Code. The README lists Claude Code as the full tier and the OpenAI Codex CLI, OpenCode, Cursor, Factory Droid, Kiro, GitHub Copilot CLI and Antigravity CLI as experimental, and says safety skills are enforced by hooks only in Claude Code and are advisory elsewhere. It lists these requirements: Claude Code, Git, Bun 1.4.2 or newer (the README calls it the tested version; it says setup refuses Bun older than 1.3.3 and warns in between) and, on Windows only, Node.js. It recommends the Aside browser on macOS 15 or newer; without it, setup builds gstack's own browser and downloads Chromium. It says /cso needs a Bun release with four build flags and a native toolchain, or it reports not assessed. Outside reviews need the Codex CLI signed in when you use Claude Code. The README says the design tools call OpenAI models by default, and that /design-shotgun on Codex needs no OPENAI_API_KEY. The repository can change at any time; check its README before you install.

Data practices

According to the README, gstack has opt-in usage telemetry, which the command gstack-config set telemetry off turns off; it keeps local usage analytics in a file on your machine, and it can optionally sync its memory to a private git repository. The README says that in team mode each Claude Code session starts with an update check, throttled to once an hour. It says plan workflows use an independent reviewer model from the other provider (GPT-6 Astra from Claude Code, Fable 5.1 from Codex), and that outside reviews need the Codex CLI or Claude Code installed and signed in. It says the design tools call OpenAI, or an OpenAI-compatible gateway if you set OPENAI_BASE_URL, and that egress receipts record the gateway host. What your coding agent sends to its model provider depends on that agent and provider.