GStack Cheat Sheet
GStack turns Claude Code into a structured development team. 28 slash commands across the full development lifecycle.
Planning
| Command | What it does | When to use |
/office-hours | YC-style brainstorm — forces key questions about demand, wedge, status quo | New idea, before any code |
/plan-ceo-review | Challenges your plan — finds the 10-star version | Strategy check |
/plan-eng-review | Locks architecture — data flow, edge cases, test coverage | Before implementation |
/plan-design-review | Rates design dimensions 0-10, fixes weak spots | UI/UX plans |
/autoplan | Runs CEO + design + eng reviews in sequence | Full review gauntlet |
/design-consultation | Creates complete design system (typography, color, spacing) | Starting new UI |
Development
| Command | What it does | When to use |
/investigate | Root cause debugging — no fixes without finding the cause | Something's broken |
/browse | Headless Chromium (~100ms per action) | Testing a live site |
/codex | OpenAI Codex second opinion — review, challenge, consult | Independent code review |
Testing & QA
| Command | What it does | When to use |
/qa | Full QA — finds bugs AND fixes them with atomic commits | Feature ready for testing |
/qa-only | Same testing, report only, no fixes | Just want a bug report |
/review | PR code review — SQL safety, trust boundaries | Before merging |
/benchmark | Performance regression, Core Web Vitals | Checking page speed |
/design-review | Visual QA — spacing, hierarchy, polish — then fixes | "Does it look good?" |
Shipping
| Command | What it does | When to use |
/ship | Full PR workflow — test, review, version bump, push | Code is ready |
/land-and-deploy | Merge PR, wait for CI, verify production | After /ship |
/canary | Post-deploy monitoring — screenshots, errors | After deploy |
/document-release | Updates README, ARCHITECTURE, CHANGELOG | After merge |
Safety
| Command | What it does | When to use |
/careful | Warns before destructive commands | Touching production |
/freeze | Restricts edits to one directory | Scoped debugging |
/unfreeze | Removes freeze restriction | Done with scoped work |
/guard | /careful + /freeze combined | Maximum safety |
/cso | Security audit — OWASP, STRIDE, secrets, supply chain | Security review |
Operations
| Command | What it does | When to use |
/retro | Weekly retrospective from git history | End of sprint/week |
/gstack-upgrade | Updates gstack to latest | New version available |
Workflow
The recommended flow: /office-hours → /autoplan → implement → /qa → /review → /ship → /canary → /document-release → /retro