gstack 1.91.52.0: /qa gets annotations.json right on the first try

3 days ago

gstack 1.91.52.0 (2026-10-08) for Claude Code users: /qa and /qa-only now get annotations.json right on the first try, because the instructions finally say the limits field is a list of strings. That saves a failed tool call and a retry near the end of a QA run. https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#191520---2026-10-08

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00The limits field
  2. 0:14Who it reaches
Show transcript

The limits field

gstack logo

gstack 1.91.52.0: /qa gets annotations.json right on the first try

"limits": { … }before: rejected
"limits": ["checkpoint 001"]now: documented
The fixWho it reaches
garrytan/gstack · CHANGELOG.md 1.91.52.0

Before writing its report, /qa saves an annotations file. Its instructions never said that the limits field must be a list of strings, so Claude often wrote an object, and the call failed. The instructions now show the list.

Who it reaches

The first try failed in 11 of 15 recent test runs

■ limits written as an object, call failed, agent retried
/qa/qa-onlyshare the fixed instructions
CHANGELOG.md · 1.91.52.0What this means for you
The fixWho it reaches
garrytan/gstack · CHANGELOG.md 1.91.52.0

In gstack's own recent test runs of /qa, Claude wrote the wrong shape in 11 of 15, so each of those runs spent a failed tool call and a retry near the end. Anyone running /qa or /qa-only could hit the same retry, and both skills get the fix.