gstack now gets Claude Code to load /review when you ask for a review
2 days ago
gstack 1.99.5.0 to 1.100.0.0: Claude Code skill lines now say when to use each gstack skill, so Opus loads /review when you ask for a review. /plan-eng-review is back, /autoplan shows a reviewer's change as a choice, locks hold on Ubuntu 26.04, /ship reviews the head that merges, and agent reports open with what failed.
Links
- github.com/garrytan/gstack/blob/main/CHANGELOG.mdgithub.com
- github.com/garrytan/gstack/blob/main/CHANGELOG.mdgithub.com
- github.com/garrytan/gstack/commits/maingithub.com
- github.com/garrytan/gstack/blob/main/docs/review-policy.mdgithub.com
- github.com/garrytan/gstack/blob/main/docs/writing-prs.mdgithub.com
- gstackgithub.com
Ask about this presentation
Chapters
0:00Skill lines say when
0:12About 840 tokens
0:24/plan-eng-review is back
0:3602 /autoplan keeps the reviewer’s objection
0:40Reviewer changes as choices
0:55Three plans, three rules
1:0803 Locks on Ubuntu 26.04
1:12Locks hold on Ubuntu 26.04
1:2704 /ship reviews the head that merges
1:30Rounds per pull request
1:41Diff-only re-checks
1:54Three plain lines
2:07No false green
2:21Big test suites
2:3405 What every gstack agent now does
2:37Bad news first
2:52Ask once, keep secrets
3:07/verify asks for the test
3:23Changelog
Show transcriptHide transcript
Ask Opus 5.5 in Claude Code to review your changes, and it loaded /review zero times in three tries. Now each gstack skill line ends with when to use it.
The skill list Claude Code loads each session grows by about 840 tokens, and only Claude Code gets the new lines. The /review line now counts local changes, so you need no pull request.
/plan-eng-review is a standalone command again on Claude Code, Codex and the other hosts, and your next setup puts it back. Requests to review the architecture route to it again.
Next, what /autoplan does when a reviewer disagrees with your plan.
The approval page used to bury a reviewer's objection under keep your direction. Now only lines quoted under Owner's words set your direction. Any other change a reviewer asks for becomes a lettered choice.
A plan without an Owner's words section gets one question confirming the direction is yours. App plans show their Day one table first. And a declined high or critical finding becomes a blocking build task.
Next, a lock failure on Ubuntu 26.04.
Ubuntu 26.04 ships a Rust mkdir that reports success even when another process made the folder first, so two updates could move one checkout at once. Every gstack lock now admits exactly one holder.
Next, how /ship reviews and opens pull requests.
The two-round review cap used to reset on every /ship run, so five ships could mean ten reviews. Now it counts per pull request, and a changed head gets a full review.
A re-check of only the diff missed all eight real faults that full review rounds caught, so it now counts as advice only. Receipts that relied on one need a fresh full review.
/ship now opens a pull request with what changed, why, and what you have to do. Every land is one commit named after the pull request, and in-house jargon stays in the Agent notes.
When a rerun created no jobs, GitHub's rollup dropped the failed attempt and the merge queue saw green. gstack-pr-wait, the land gate and the release cut now read every attempt and keep the worse answer.
A suite with thousands of test files now runs on Linux instead of hitting the argument limit. A step that runs out of time says so, and you can set its budget. Remote test runs get the same fix.
Last, the rules every gstack agent now follows.
Every status report now stays under 250 words and opens with three lines: what failed or was skipped, what the agent didn't check, and what else it changed. Each line names every item or says none.
Every skill, on every host, now tells the agent to ask each question once and to clear placeholders from any file it hands over. It also bars printing a whole environment or git config, where tokens can leak.
With /verify loaded, Opus 5.5 already ran a test after its last edit in almost every run, so the optional Stop hook stopped checking. Skills you wrote that list that check now skip only that item.
I would say yes, if you work in Claude Code, where the new skill lines load, and you run setup again for /plan-eng-review. The skill loading gain was measured on Opus 5.5 alone. The gstack changelog has the rest.
Up next
3:26gstack 1.102.0.0 loads the right skill and guards rm -rf in Claude Code
@gstack
11 hours ago
3:14gstack 1.101.0.0 keeps a token-capped /ship going in Claude Code
@gstack
1 day ago
1:26gstack 1.99.4.0: /ship keeps its second-model review when OpenAI refuses it
@gstack
5 days ago
0:57gstack 1.99.3.0: /ship stops refusing Next.js and SvelteKit route files
@gstack
6 days ago
1:48gstack's browser skills work again in Codex and Cursor
@gstack
1 week ago
3:18gstack 1.98.0.0 drops /investigate and /plan-eng-review, and new installs go stable
@gstack
1 week ago
3:11gstack 1.97.0.0’s browser stops trusting compromised certificates, and /investigate can demand a root cause
@gstack
1 week ago
3:12gstack’s /land-and-deploy now waits for you to type it, and /runaway-stopper catches runaway agents
@gstack
2 weeks ago
3:18gstack’s browser moves to Chromium 156, and /ship stops pushing merge conflicts
@gstack
2 weeks ago
3:21gstack’s new Claude Code hooks pick the right skill and check it finished
@gstack
2 weeks ago
1:37gstack’s /autoplan now runs a CEO review that asks you nothing
@gstack
2 weeks ago
1:59gstack now installs into Gemini CLI, and draws mockups with Gemini
@gstack
2 weeks ago