Which agents work with it?

Any agent that reads skills from a directory. Claude Code, Codex and Gemini CLI read it natively; Cursor and VS Code connect over MCP.

The voice runs on your own machine, so there is nothing to meter. The first run downloads it, about 340 MB.

Yes. The skill is MIT-licensed and the authoring format is public.

Create

gstack’s /ship now asks before stamping a version its PR queue check couldn’t verify

1 hour ago

@gstack Subscribe

gstack 1.91.190.0 to 1.91.191.0 (2026-10-25): when the PR version queue check comes back incomplete, /ship now reruns it once and asks whether to use the provisional version or stop, instead of writing it as verified. /ship's version write also moves your [Unreleased] CHANGELOG entry under the new version. Release notes: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911910---2026-10-25 https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911900---2026-10-25 Commits: https://github.com/garrytan/gstack/commits/main

Ask about this presentation

Show transcript

Queue check

gstack’s /ship now asks before stamping a version its PR queue check couldn’t verify

Before · an incomplete check printed a warning, then wrote the provisional version anyway

Now · it reruns the check once, then asks: use the candidate, or stop

Queue checkChangelogNext

garrytan/gstack · CHANGELOG.md · 1.91.191.0

When gstack couldn't check every open PR's version, /ship still wrote its provisional pick as if the queue were clear. Now it rechecks once, then asks you: use that candidate, or stop.

Changelog

/ship now moves your Unreleased changelog entry under the new version

## [Unreleased]

## [<version>] - <UTC date>

Kept · every entry; only the heading changes

Left alone · a released heading, or a file with no Unreleased section

Queue checkChangelogNext

garrytan/gstack · CHANGELOG.md · 1.91.191.0

The Unreleased heading in your changelog used to need renaming by hand. /ship now moves that entry under the new version and date. Only the heading changes, and a released heading stays put.

If your repo keeps several PRs open at once, I would upgrade before the next /ship

CHANGELOG.mdgarrytan/gstack · 1.91.191.0

Queue checkChangelogNext

garrytan/gstack · CHANGELOG.md · 1.91.191.0

If your repo keeps several PRs open at once, I would upgrade gstack before your next /ship, because that is where an unchecked version used to slip through. The details are in the gstack changelog.