Gstack
Install and use gstack in Capy and Claude Code. Load at session start to check this machine, and for gstack planning, code review, debugging, QA, design, security, documentation, and shipping workflows.
Install
npx skills add garrytan/gstack --skill gstackgit clone --depth 1 https://github.com/garrytan/gstack.git /tmp/gstack
mkdir -p ~/.claude/skills
cp -r /tmp/gstack/capy/skill/gstack ~/.claude/skills/gstackPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# gstack for Capy and Claude Code ## Session start: check, then install only when needed **Crew lanes:** after this check passes, read [lane-card.md](lane-card.md), not the rest of this file; it says what to read before /ship. Resolve `scripts/install.sh` relative to this SKILL.md, not the working repository. It is a frozen bootstrapper: it prints `gstack-capy-skill: wrapper <n> (<path>)` first, learns the supported minimum from gstack's remote, and hands over to the checkout's own wrapper (`bin/gstack-capy-session`). 1. At session start run `bash scripts/install.sh --check`, adding `--for <skill>` when you know the workflow (`--for autoplan`, `--for review`, `--for qa`). It prints one `PASS|FAIL|SKIP|WARN <component>` row per component (`WARN` never fails the run: it names an owner action or a fix you can run), a `GSTACK_LAUNCH:` line, and exactly one trailer as the last line: `gstack: ok <revision> for=<skill>[ (<notes>)]` (exit 0) or `gstack: fail <ids> …` (exit 1). Read the exit status and grep `^gstack: ` directly; never pipe the check through `tail`, `head` or `grep` alone. `--check` never moves the checkout. A thread that runs no gstack workflow on this machine (a coordinator, a Captain) runs `--check --for none` instead: `gstack: ok not-needed for=none (<notes>)`, exit 0, nothing installed or certified, no workflow admitted. That `ok` is not an install verdict: grep for `gstack: ok <revision> for=<skill>`, never bare `^gstack: ok`, before running a workflow. Record
Details
- Skill name
gstack- Repository
- garrytan/gstack
- Path
capy/skill/gstack/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Gstack skill do?
Install and use gstack in Capy and Claude Code. Load at session start to check this machine, and for gstack planning, code review, debugging, QA, design, security, documentation, and shipping workflows.
How do I install the Gstack skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add garrytan/gstack --skill gstack. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Gstack popular?
It lives in garrytan/gstack, which has 141,991 GitHub stars and 20,959 forks, and is included in 2 curated skill lists.
Related skills
Autoplan
142kgarrytan/gstack
Auto-review pipeline — runs the CEO, design, eng and DX reviews in order (lean run: one reviewer), auto-deciding. Use for: run all reviews, automatic review pipeline. (gstack)
Benchmark
142kgarrytan/gstack
Web performance regression detection. Use for: web performance benchmark, check page speed. (gstack)
Benchmark Models
142kgarrytan/gstack
Cross-model benchmark for gstack skills. Use for: cross model benchmark, compare claude gpt gemini. (gstack)
Gstack Openclaw Office Hours
142kgarrytan/gstack
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
Devex Review
142kgarrytan/gstack
Live developer experience audit. Use for: live dx audit, test developer experience. (gstack)
Gstack Plan
142kgarrytan/gstack
Use before building a feature: challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build. (gstack)
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.