gstack now auto-runs only four skills, so it stops colliding with other skill packs
2 hours ago
gstack 1.91.216.0 to 1.91.243.0 (2026-10-25 to 2026-10-26): gstack for Claude Code now auto-invokes only /office-hours, /review, /qa and /ship by default, team installs follow a weekly stable release, a fresh install is about 520 MB smaller, API keys stay out of tool output, /review re-checks only its fixes, and skills start at once on Windows again. Plus a browser TLS caveat. Changelog: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md Release channels: https://github.com/garrytan/gstack/blob/main/docs/releases.md Proactive setting: https://github.com/garrytan/gstack/blob/main/docs/proactive.md Browser TLS warning: https://github.com/garrytan/gstack/blob/main/BROWSER.md Commits: https://github.com/garrytan/gstack/commits/main
Ask about this presentation
Chapters
Show transcriptHide transcript
gstack used to start any skill that matched your request, which made it collide with other skill packs in Claude Code. Now only /office-hours, /review, /qa and /ship start on their own.
Team-mode installs used to move with every merge on main, about a dozen a day. Now they follow a stable branch that a Monday release moves to the newest green commit, plus hotfixes.
Setup now installs production dependencies only, so a fresh install skips the test toolchain and the Claude Agent SDK's native binaries. An install you already have keeps them until you clear them.
In an unattended /ship run, a child agent ran a bare export and printed API keys into its tool output. Now children get a file to source, and redaction stops any key from your environment reaching a PR body.
Each /review fix cycle used to re-read the whole branch, so big branches hit the three-cycle stop. Now the next pass reads only the fixes, and the final pass still covers everything.
In Git for Windows, the workflow lock relied on a symlink that never got created, so each skill start waited out three hundred retries, over eight minutes in one report. Now skills start right away.
/context-restore now flags commits that landed after a save. A design doc edited in plan mode stays current for the plan reviews. And /design-html builds landing pages around one visitor action, without invented customers or numbers.
gstack's headless browser gets no revocation updates, so it still trusts the eMudhra certificates Chrome blocked. Until Playwright ships a fixed Chromium, keep signed-in work off untrusted networks. If other skill packs share your Claude Code, I would upgrade now.
Up next
0:55gstack's unattended /ship stops handing the parent agent a stale receipt
@gstack · 22 hours ago
1:05gstack's /careful stops asking about words in your commit messages
@gstack · 23 hours ago
0:50gstack's /ship and /review now see your Python tests
@gstack · 1 day ago
0:59gstack 1.91.206.0 lets pregate clear CI lanes your machine can run
@gstack · 1 day ago
1:05gstack’s /ship can now re-review only your fixes
@gstack · 1 day ago
0:54gstack now fixes a bug you have already diagnosed without opening /investigate
@gstack · 1 day ago
0:43gstack’s /ship and /plan-eng-review now rank every finding CRITICAL or INFORMATIONAL
@gstack · 1 day ago
1:16gstack’s /ship now stops when the second-opinion review says not ready
@gstack · 1 day ago
1:07gstack’s /land-and-deploy stops halting parallel PRs on a false VERSION drift
@gstack · 1 day ago
1:07gstack’s Memorable recall now works in read-only repos you opt in
@gstack · 1 day ago
1:07gstack 1.91.192.0: merge trains stop passing a damaged CHANGELOG
@gstack · 1 day ago
0:40gstack’s /ship now asks before stamping a version its PR queue check couldn’t verify
@gstack · 1 day ago







