Thanks to visit codestin.com
Credit goes to github.com

Skip to content

doronkatz/gstack-codex

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

93 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

gstack

gstack is a Codex-native workflow bundle: structured skills for planning, review, QA, release work, plus a fast persistent headless browser for real product testing.

This repo is intentionally scoped to Codex. The canonical install surfaces are:

  • Global install: ~/.codex/skills/gstack
  • Vendored install: .codex/skills/gstack
  • Project instructions: AGENTS.md

What you get

  • Workflow skills for ideation, engineering review, design review, debugging, QA, release, docs, and retros.
  • A compiled browse binary backed by persistent Chromium and Playwright.
  • Shared conventions for review status, documentation upkeep, and Codex-first project instructions.

Quick start

Requirements:

  • Codex CLI
  • Git
  • Bun 1.0+

Install globally:

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

Add to a repo so teammates get the same setup:

mkdir -p .codex/skills
cp -Rf ~/.codex/skills/gstack .codex/skills/gstack
rm -rf .codex/skills/gstack/.git
cd .codex/skills/gstack
./setup

Add this to your repo’s AGENTS.md:

## gstack

Use gstack `/browse` for browser work. Prefer it over generic browser MCP tools when you need persistent state, screenshots, diffs, or cookie-backed sessions.

Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /investigate, /document-release, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade.

Core workflow

gstack is designed around a single sprint loop:

Think → Plan → Build → Review → Test → Ship → Reflect

Typical flow:

  1. /office-hours
  2. /plan-ceo-review
  3. /plan-eng-review
  4. implement
  5. /review
  6. /qa
  7. /ship
  8. /document-release
  9. /retro

Skills

Skill Purpose
/office-hours Reframe the product problem before implementation
/plan-ceo-review Pressure-test scope and product direction
/plan-eng-review Lock architecture, sequencing, tests, and edge cases
/plan-design-review Review design completeness before building
/design-consultation Create a product design direction and system
/review Primary Codex-native pre-landing code review
/investigate Root-cause debugging workflow
/design-review Design audit plus fixes
/qa Browser-based QA with fixes
/qa-only Browser-based QA without code changes
/ship Release workflow: tests, changelog, PR prep
/document-release Update docs after code changes
/retro Weekly engineering retrospective
/browse Persistent browser for testing and screenshots
/setup-browser-cookies Import cookies from a real browser
/careful Destructive-command guardrails
/freeze Restrict edits to one directory
/guard /careful + /freeze
/unfreeze Clear the freeze boundary
/gstack-upgrade Update gstack itself

Docs

Troubleshooting

/browse not found:

cd ~/.codex/skills/gstack
./setup

Vendored install is stale:

/gstack-upgrade

Local dev mode:

bin/dev-setup

License

MIT

About

Use Garry Tan's exact Claude Code setup: 15 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA. This fork is for codex

Resources

License

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • TypeScript 72.1%
  • Go Template 25.6%
  • Shell 2.3%