Integrating gstack with Claude Code: Complete Installation and Optimization Guide

gstack is an open-source skillset developed by @garrytan (President of Y Combinator), providing a system of slash commands like /review, /qa, and /office-hours to structure Claude Code’s workflow into standardized technical processes, eliminating the need to type lengthy, distracting prompt chains.

Guide to Integrating gstack into Claude Code: Installation and Optimization Workflow — Operational architecture: Integrating gstack into Claude Code

1. What is gstack and why should developers integrate it?

When using vanilla Claude Code, you often have to repeat long prompts: “Please review this diff carefully, check for race conditions, find security flaws, and verify logic”. This not only consumes context tokens but also lacks consistency across sessions.

gstack solves this problem by packaging real-world engineering practices into shortcut commands (skills):

Workflow Standardization: Simply type a short command like /review or /qa, and Claude Code will automatically trigger a chain of in-depth tasks.
Browser QA with a “Vision”: Automatically opens a headless browser via Playwright, performs exploratory clicks on the staging URL, takes screenshots, and inspects real-world console logs.
Token Cost Optimization: gstack commands are finely tuned to be concise, eliminating verbose boilerplate and focusing directly on source code analysis.

CORE BENEFITS

After installing gstack, you instantly gain 4 powerful commands: /review (code review), /qa (real-world web testing), /office-hours (architectural shaping), and /ship (release preparation), turning Claude Code into a virtual Senior Tech Lead working right by your side.

2. System Requirements and Environment Preparation

To install gstack smoothly without dependency errors, prepare the following foundational tools beforehand:

1. Required Tools

Claude Code CLI (from Anthropic).
Git (to clone the repository from GitHub).
Bun version v1.0 or higher.

2. By Operating System

macOS / Linux: Git and Bun are all you need.
Windows: Requires Node.js LTS installed and must be run using PowerShell as Administrator.

If your computer does not have Bun yet, open your Terminal and install it quickly using the following command:

Install Bun

curl -fsSL https://bun.sh/install | bash

After installing Bun, restart your Terminal so the system recognizes the bun command before moving on to the next step.

3. Step-by-step guide to installing gstack

The gstack installation process is fully automated with just a single command line. Choose the command corresponding to your operating system:

Step 3.1: Run the automated installation command

For macOS / Linux (open Terminal and run):

macOS / Linux

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

For Windows PowerShell (run as Administrator):

Windows

New-Item -ItemType Directory -Force "$env:USERPROFILE.claudeskills" | Out-Null
cd "$env:USERPROFILE.claudeskills"
git clone https://github.com/garrytan/gstack.git
cd gstack
.setup.ps1

HOW IT WORKS

The setup script downloads dependencies, compiles the required skills, and links the gstack directory to ~/.claude/skills/ so Claude Code automatically loads it every time you launch your project.

Step 3.2: Launch Claude Code and verify detection

Open any coding project folder on your computer, then launch Claude Code:

Launch Claude Code

claude

Try typing a forward slash / in the Claude Code prompt interface. If you see the list of commands /review, /qa, and /office-hours appear, the system is 100% successfully installed.

4. Three core slash commands to get started

Below are the 3 most important practical commands you should use daily to get the most out of gstack:

1. /office-hours: Shaping Initial Architectural Thinking

Use this when starting a new project or preparing to build a complex feature. Claude will take on the role of a Senior Architect to interview you, break down the problem, and define the technical workflow before writing any code:

Startup Command

/office-hours

2. /review: Production-Grade Code Review

Inspect the entire current git diff against the strictest standards: catch race conditions, check edge cases, protect trust boundaries, and identify potential security vulnerabilities:

Code Review Command

/review

3. /qa: Test the UI Directly on the Staging URL

Completely different from AI blindly guessing code, the /qa command launches a headless browser to access your actual URL, test-click buttons, catch red console errors, and capture verification screenshots:

QA Test Command

/qa https://your-staging-url.com

5. Share gstack into the project repo for the entire team

If you work in a team, add gstack directly into the project’s repository. This ensures that whenever any member clones the source code, they will have the synchronized toolset ready to go without needing individual installations:

Copy command on macOS / Linux:

Team Sync (Mac/Linux)

cp -Rf ~/.claude/skills/gstack .claude/skills/gstack && rm -rf .claude/skills/gstack/.git && cd .claude/skills/gstack && ./setup

Copy command on Windows PowerShell:

Sync for Team (Windows)

New-Item -ItemType Directory -Force ..claudeskills | Out-Null
Copy-Item -Recurse -Force $HOME.claudeskillsgstack ..claudeskillsgstack
Remove-Item -Recurse -Force ..claudeskillsgstack.git
cd ..claudeskillsgstack
.setup.ps1

TEAM NOTE

After running the command above, commit the .claude/skills/gstack directory to your project’s Git repository. Your teammates only need to pull it to start using it immediately.

6. Update gstack to the Latest Version

The gstack community continuously adds new skills and patches compatibility fixes for the latest versions of Claude Code. When an update notification appears, simply run the following command:

Update gstack

cd ~/.claude/skills/gstack && git pull && ./setup

If you have shared gstack within your project’s repository, do the same inside the repo’s .claude/skills/gstack directory and commit the changes so the entire team can use the latest version.

7. Common Errors and Troubleshooting

If you encounter issues during the installation or operation of gstack, select the corresponding error below to resolve it quickly in 1-2 steps:

Error: command not found: bun when running the setup command
▼

Cause: Bun is not installed on your computer, or Bun’s binary path has not been exported to your PATH environment variable.
Solution: Re-run the Bun installation command: curl -fsSL https://bun.sh/install | bash, then run source ~/.bashrc (or source ~/.zshrc on macOS), and verify with the command bun --version.

Error: permission denied when running ./setup
▼

Cause: The setup script file lacks executable permissions.
Solution: Navigate to the gstack directory and grant executable permissions using the command: chmod +x setup.sh ./setup, then run ./setup again.

Claude Code starts but does not recognize /review, /qa commands
▼

Cause: The skills directory is in the wrong location, or Claude Code has not reloaded its configuration.
Solution: Check if the ~/.claude/skills/gstack directory exists. Ensure the skill.json configuration file is located directly inside this directory. Exit the Claude Code process completely and restart it using the claude command.

Error on Windows: ExecutionPolicy blocks running setup.ps1
▼

Cause: Windows PowerShell security policy blocks the execution of downloaded external scripts by default.
Solution: Open PowerShell as Administrator and run the command: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser, press Y to confirm, then run the installation script again.

Error: /qa command fails to take screenshots or browser crashes
▼

Cause: Playwright browser drivers are not fully installed on your operating system.
Solution: Navigate to the gstack directory and run the command to install the browser engines: bunx playwright install --with-deps to add the required system dependencies.

Error: Version conflict with older Claude Code CLI
▼

Cause: gstack requires the latest Claude Code APIs to handle slash commands.
Solution: Upgrade Claude Code to the latest version using the command: npm install -g @anthropic-ai/claude-code or bun install -g @anthropic-ai/claude-code.

8. Frequently Asked Questions (FAQ)

Quick answers to common questions about the performance and operation of gstack:

Can gstack be used with a free Claude account?
▼

No. Claude Code CLI currently requires a paid account (Claude Pro, Team, or Enterprise) or an API Key from the Anthropic Console for command-line programmatic access.

Can I create my own custom slash commands in gstack?
▼

Absolutely. The gstack architecture is very open. You only need to add a markdown file defining the new prompt to the skills/ directory of gstack and declare the command in the configuration file, and Claude Code will automatically detect your new slash command.

Can the /qa command test internal websites (localhost)?
▼

Yes. Since the browser runs directly on your local machine, the command /qa https://devpixelvn.com:3000 can fully access, interact with, and take screenshots of the website currently in development just like a real user.