Fixes
gstack’s /ship can now re-review only your fixes
every fix cycle → whole branchOn a large branch, each gstack /ship fix cycle reran every specialist and the Red Team over the whole branch, and often hit the three-cycle stop. Now the pass after a fix can review just what changed.
Final
A fixes-only pass can never be the review that ships
A narrowed review is always logged as unverified, so it can never clear the branch to ship. One full pass over the whole branch still has to come last before /ship moves on.
Fallback
Some repeats still run as a full pass
/ship falls back to a full review when there is no earlier fixing pass to narrow from. If you start work and then ship, the first repeat stays full, and so does any repeat after a rebase.
Unattended
Unattended /ship, /review and /qa no longer promise a result line
Unattended gstack skills were all told to end with a result line only /autoplan and /eval-plan write. Now ship, review and /qa stop at their first pending item and name the record a parent reads.
Verdict
If /ship’s fix loop keeps hitting its three-cycle stop, I would upgrade now
CHANGELOG.mdgarrytan/gstack · 1.91.204.0 to 1.91.205.0If /ship keeps running out of fix cycles on your big branches, I would upgrade gstack now. Repeat reviews get smaller, and a full pass still decides what ships.
















