| name | ost-garrytan-gstack-install |
| description | Help users install or update gstack. Primary path: run the support package install script; fallback to repo_readme_summary.md when the script is unavailable or manual control is needed. Scope: install, update, host selection, optional team mode, and verification guidance; excludes uninstall and detailed usage tutorials. |
| argument-hint | [--host=claude|codex|opencode|cursor|factory|slate|kiro|hermes|gbrain] [--team=none|required|optional] [--install-dir=DIR] |
gstack Install (skill_for_setup)
Reference: repo_readme_summary.md
Script: scripts_for_install/install.sh
Upstream repository: garrytan/gstack
When to Use
Use this skill when the user wants to install, update, configure, or verify gstack for Claude Code or another supported AI agent host.
This skill is for setup only. It does not provide a full gstack tutorial and does not uninstall gstack.
Pre-read
../../repo_readme_summary.md - install methods, prerequisites, platform notes, and verification guidance.
../../scripts_for_install/install.sh - supported flags, host names, platform detection, and script behavior.
../../.ost-refs/ if it exists - local package references.
Pre-checks
Confirm these from conversation context or ask only when needed:
| Information | Default | Why it matters |
|---|
| Operating system | None | The script supports macOS, Linux, WSL, and Git Bash/MSYS on Windows 11. |
| Target host | claude | Controls whether the script runs ./setup or ./setup --host HOST. |
| Team mode | none | required or optional modifies the current project through gstack-team-init. |
| Install directory | ~/.claude/skills/gstack | Existing non-git paths cause the script to stop and ask for cleanup or a different directory. |
Procedure
Primary path: run the install script
Use this path on supported shell platforms: macOS, Linux, WSL, and Git Bash/MSYS on Windows 11.
From the support package root, run:
sh scripts_for_install/install.sh
Common examples:
sh scripts_for_install/install.sh
sh scripts_for_install/install.sh --host=codex
sh scripts_for_install/install.sh --host=cursor --install-dir="$HOME/gstack"
sh scripts_for_install/install.sh --team=optional
sh scripts_for_install/install.sh --team=required
The script:
- checks for
git and bun;
- also checks for
node on WSL or Git Bash/MSYS because upstream browser fallback support needs it there;
- clones or updates
https://github.com/garrytan/gstack.git;
- runs upstream
./setup for Claude Code or ./setup --host HOST for non-Claude hosts;
- optionally runs
bin/gstack-team-init required|optional.
Fallback path: use repo_readme_summary.md
Use the fallback path when:
- the platform is not supported by the script;
- the user wants to execute commands manually;
- the script fails before reaching upstream setup;
- a Windows setup requires manual handling of Git Bash, WSL, Node.js, or copied files after
git pull;
- the user needs OpenClaw-specific ClawHub installation rather than the host setup script.
Follow repo_readme_summary.md Section 2: Installation and Updates. Send commands to the user for confirmation before running them one by one.
Verification
Upstream gstack does not publish a standalone --version or doctor command in the local summary. Use the smallest relevant confirmation:
cd ~/.claude/skills/gstack && ./setup
For browser capability build failures, use the upstream recovery/build confirmation:
cd ~/.claude/skills/gstack && bun install && bun run build
Then ask the user to restart the target agent and try an appropriate slash command:
/office-hours
/review
/qa https://example.com
If Claude Code cannot see gstack skills, follow repo_readme_summary.md Section 2 and add the upstream ## gstack guidance and slash-command list to CLAUDE.md.
Tell the User After Install
gstack is installed or updated. Restart the target agent or start a new session, then try /office-hours, /review, or /qa https://example.com. Updates can also be requested with /gstack-upgrade where supported.
Troubleshooting
| Symptom | Likely cause | Handling |
|---|
missing required command: git | Git is not on PATH. | Install Git, then rerun the script. |
missing required command: bun | Bun v1.0+ is not on PATH. | Install Bun, then rerun the script. |
missing required command: node on WSL or Git Bash/MSYS | Windows browser fallback support needs Node.js. | Install Node.js and ensure it is on PATH, then rerun the script. |
| Install directory exists but is not a git checkout | The target path contains unrelated files. | Move it aside or rerun with --install-dir=DIR. Do not delete user files automatically. |
| Skills are not visible after install | The agent session has not reloaded or project guidance is missing. | Restart the target agent. For Claude Code, add the upstream gstack section and slash-command list to CLAUDE.md if needed. |
| Windows without Developer Mode loses symlink behavior | Upstream setup copies files instead of symlinking. | After future git pull updates, rerun cd ~/.claude/skills/gstack && ./setup. |
| Browser commands fail after setup | Browser build/dependency state may be incomplete. | Run cd ~/.claude/skills/gstack && bun install && bun run build. |
| User asks to uninstall | Uninstall is outside setup scope. | Point to upstream README uninstall guidance or ~/.claude/skills/gstack/bin/gstack-uninstall; do not run uninstall by default. |