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.

Ask about this presentation

Chapters

  1. 0:00Skill lines say when
  2. 0:12About 840 tokens
  3. 0:24/plan-eng-review is back
  4. 0:3602 /autoplan keeps the reviewer’s objection
  5. 0:40Reviewer changes as choices
  6. 0:55Three plans, three rules
  7. 1:0803 Locks on Ubuntu 26.04
  8. 1:12Locks hold on Ubuntu 26.04
  9. 1:2704 /ship reviews the head that merges
  10. 1:30Rounds per pull request
  11. 1:41Diff-only re-checks
  12. 1:54Three plain lines
  13. 2:07No false green
  14. 2:21Big test suites
  15. 2:3405 What every gstack agent now does
  16. 2:37Bad news first
  17. 2:52Ask once, keep secrets
  18. 3:07/verify asks for the test
  19. 3:23Changelog
Show transcript
  1. 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.

    Slide text
    gstack logo

    gstack now gets Claude Code to load /review when you ask for a review

    “Review my changes before I land them”
    /review loaded 0 of 3 times
    “plan this feature”
    no gstack skill in 9 tries
    + Use for: review my changes, look over my diff, review this pr.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  2. 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.

    Slide text

    The longer skill list costs about 840 tokens per Claude Code session

    Claude Code only: other hosts and the full catalog keep their old lines
    /review: local changes and a branch count, with or without a pull request
    /plan-eng-review: says it plans a feature before you build it
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  3. /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.

    Slide text

    /plan-eng-review is back as its own command

    $ ./setup
    → /plan-eng-review installed again
    “review the architecture”
    → /plan-eng-review
    Claude Code, Codex, the other external hosts and OpenClaw. /autoplan is unchanged.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.99.5.0
  4. Next, what /autoplan does when a reviewer disagrees with your plan.

    Slide text
    02

    /autoplan keeps the reviewer’s objection

    Skills Plans Locks /ship Agents
  5. 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.

    Slide text

    /autoplan now shows a reviewer’s change to your plan as a choice, and recommends it

    Your direction: only lines quoted under ### Owner’s words
    Everything else: scope, build order, cost or packaging
    On the page: a lettered choice, even from one reviewer at any severity
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  6. 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.

    Slide text

    Three kinds of plan get their own handling on the approval page

    No Owner’s words: one question asks you to confirm the direction is yours
    App plans: the ### Day one table shows first, and each guessed row becomes a question
    Declined High or Critical finding: the plan stays, and the finding goes into the build as a blocking task
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  7. Next, a lock failure on Ubuntu 26.04.

    Slide text
    03

    Locks on Ubuntu 26.04

    Skills Plans Locks /ship Agents
  8. 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.

    Slide text

    gstack’s locks hold again on Ubuntu 26.04 and GitHub’s ubuntu-latest

    $ mkdir "$LOCK" # Rust coreutils 0.8.0
    exit 0, though another process made it first
    8 parallel config writers → 6 keys lost
    gstack_lock_take → exactly one holder
    GitHub’s ubuntu-latest ships it from 2026-11-09. Updates, gstack-config, setup and the browser install all take the new lock.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  9. Next, how /ship reviews and opens pull requests.

    Slide text
    04

    /ship reviews the head that merges

    Skills Plans Locks /ship Agents
  10. 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.

    Slide text

    /ship counts review rounds per pull request, and the head that merges gets a full review

    Before: the two-round cap reset on every /ship run, so five ships meant up to ten reviews
    Now: a new head whose own lines changed gets a fresh full review
    At two full rounds: one read-only review, and its blocker goes to the Captain
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  11. 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.

    Slide text

    A re-check of only the changed lines no longer clears a pull request

    Full review rounds
    8 of 8 real faults caught
    Diff-only re-check
    0 of 8
    Now advice only. A receipt carried by an older re-check needs a fresh full review.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  12. /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.

    Slide text

    Pull requests from /ship open with three plain lines, and each merge lands as one commit

    Opening: what changed, why, and what you have to do, with the rest folded
    Merge commit: <title> (#n), the opening lines and the co-author trailers
    Plain words: pregate, receipt, lane and other in-house terms stay below the Agent notes
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  13. 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.

    Slide text

    gstack no longer calls a commit green while one of its checks failed

    rerun attempt: no jobs created
    rollup: green
    gstack-pr-wait --until green → check failed: checks
    land gate → VERDICT FAIL
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  14. 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.

    Slide text

    /ship’s test step runs big suites on Linux and says when it ran out of time

    Thousands of files: split into runs of about 96 KB instead of stopping on E2BIG
    Time limit: PREGATE: time limit hit, with a budget you can set
    Remote backend: the file list reaches the VM in a setup script
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  15. Last, the rules every gstack agent now follows.

    Slide text
    05

    What every gstack agent now does

    Skills Plans Locks /ship Agents
  16. 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.

    Slide text

    gstack agents open every status report with what failed and what they didn’t check

    Failed or skipped: every item, or none
    Unverified: every item, or none
    Also changed: every item, or none
    …the rest, under 250 words
    Lists over 10 show the top 10 and a count. Capy crews use the same shape.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  17. 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.

    Slide text

    Every gstack skill now tells the agent to ask once, check its files and keep secrets off screen

    Ask once: after checking what it can, then list it as one waiting line
    Before handing over: open the file and remove TODOs, placeholders and broken links
    Never print: a whole environment, git config --list or ps aux
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  18. 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.

    Slide text

    The Stop hook drops its test-after-edit check, and /verify asks for the run instead

    Opus 5.5 with /verify: tested after its last edit
    96% of runs
    GPT-6.1 Sol with /verify
    89% of runs
    Your own skill contract that lists check_after_last_edit skips only that item, with a SKILL_CONTRACT_SKIPPED line.
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.100.0.0
  19. 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.

    Slide text
    gstack logo

    Use gstack in Claude Code? Take this one.

    gstack CHANGELOG.md
    Rounds per pull request: docs/review-policy.md · Pull request format: docs/writing-prs.md
    Skills Plans Locks /ship Agents
    garrytan/gstack · CHANGELOG.md · 1.99.5.0, 1.100.0.0

What happened in AI today, in your inbox

One short email each evening. Read it and you’re caught up.

Built with ❤️ in New York