Phuriwaj

gstack — Post-Coding Workflow Commands

gstack — Post-Coding Workflow Commands

Garry Tan’s gstack provides 23 opinionated Claude Code tools for the full dev sprint: Think → Plan → Build → Review → Test → Ship → Reflect.

Repo: github.com/garrytan/gstack

Why / When to Use

Use after finishing a coding session to systematically review, test, and ship code without manual steps. Designed for autonomous or semi-autonomous development.

Core Concept / Commands

Standard post-coding sequence

/review          → Staff Engineer review: finds bugs, auto-fixes obvious ones
/qa <staging-url> → QA Lead: browser-tests the app, fixes bugs, adds regression tests
/ship            → Release Engineer: syncs main, runs tests, opens PR
/land-and-deploy → Merges PR, waits for CI/deploy, verifies production health
/canary          → (optional) Monitors for console errors / perf regressions post-deploy

Situational commands

SituationCommand
Something broke/investigate
Need second AI opinion (OpenAI Codex)/codex
Update docs after shipping/document-release
Security audit before shipping/cso
Design looks off/design-review
Working on prod, want guardrails/guard

Key Options / Variants

Sprint order: Think → Plan → Build → Review → Test → Ship → Reflect

Minimum viable post-coding flow: /review → /qa <url> → /ship → /land-and-deploy

Gotchas

  • /qa requires a running staging URL — run npm run dev or deploy to staging first.
  • /ship bootstraps test frameworks automatically if none exist.
  • /land-and-deploy is irreversible — only run after PR is approved.

Source

Conversation: “Identifying the next command after coding” — 2026-05-30