What gstack is

gstack is an open-source collection of role-based workflows for AI coding agents. It adds repeatable product discovery, technical planning, review, QA, security, and shipping routines rather than relying on an improvised prompt for every task.

Requirements and precautions

  • Git
  • A supported agent host such as Codex or Claude Code
  • Bun 1.0 or later where required by the repository
  • On Windows, Git Bash or WSL for the Unix-style ./setup script

The installer writes to user-level skill folders. Inspect the current repository and setup script, then back up custom agent configuration before installation.

Install for Claude Code

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

Restart Claude Code and confirm that commands such as /office-hours, /review, and /qa are available.

Install for Codex

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

Restart Codex after setup. Review the directories created under the Codex skills location and keep the installed version consistent across a team.

A practical first workflow

  1. Use /office-hours to clarify the problem and user need.
  2. Use /plan-ceo-review to challenge scope and product value.
  3. Use /plan-eng-review to inspect data flow and failure paths.
  4. Implement the approved plan.
  5. Run /review on the actual diff.
  6. Use /qa against a safe test URL.
  7. Consider /ship only after tests, permissions, and external effects are clear.

You do not need every workflow for a small change. Planning, review, and QA provide a manageable starting set.

Operational risks

Agent workflows can become too heavy for minor edits. Shipping commands can affect repositories and deployments, while browser workflows may use authenticated sessions. Confirm the target, account, branch, and side effects before executing external actions.

Updating gstack

Read release notes and repository changes before pulling a new version. Re-run the setup only when the documented update process requires it, and recheck local customizations afterward.