* Say when to use each gstack skill in Claude Code's skill list (GST-2774) Claude Code's listing of each gstack skill now keeps a short when-to-use clause after its first sentence, so Opus 5.5 loads /review on "review my changes" and /plan-eng-review on "plan this feature" (GSTA-558). Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Keep /review and /plan-eng-review within their size pins and refresh budgets CI on the first head found five size and fact checks the new catalog clause moved: the per-host SKILL.md size pins, the context-budget ceilings, the deslop-shared-libs catalog byte pin, the Claude ship golden and the catalog ceiling CLAUDE.md states. /review's and /plan-eng-review's full descriptions are now shorter than before, so their pins go down, and /plan-eng-review's scope gate is unchanged from main. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Say which skills keep no when-to-use clause in the changelog entry Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Update the catalog budget and voice-trigger docs for the when-to-use clause Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Drop "deploy this" from /ship's Claude Code skill list line Deploying belongs to /land-and-deploy, so /ship's when-to-use clause keeps "ship it, create a pr, push to main" only. Budgets, the size ledger and the Claude ship golden are re-measured. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: pre-landing review fixes Review-Finding: p1/specialist-batched#1 reader=specialist-batched Review-Finding: p1/red-team#1 reader=red-team Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Re-measure the setup-gbrain size cap after merging main Main grew setup-gbrain's always-loaded part to 38,621 bytes, and this branch's when-to-use clause adds 55 more, so the cap measured on the old base (38,637) is stale. The cap is now the merged measurement, 38,676. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
1.3 KiB
Voice input (AquaVoice, Whisper, etc.)
Many gstack skills list speech-to-text aliases (voice-triggers: in their
templates): "security check" for /cso, "run QA" or "test the app" for /qa,
"tech review" for /plan-eng-review. Say one of those naturally and the right
skill can be picked without the slash command name. On Claude Code the aliases
are routing lines in the root /gstack router; on Codex and the other hosts
they are appended to each skill's description, which is what those hosts match
on.
The separate triggers: list in a skill's frontmatter is gstack metadata, not a
matching surface. Claude Code and Codex choose a skill from its name and
description, so a phrase that appears only under triggers: does not activate
the skill (Codex output drops the field; the GBrain host keeps it). The four core
skills (/office-hours, /review, /qa, /ship) carry their triggers: phrases in
the full description itself. On Claude Code, the one-line catalog entry for most
skills also ends with a short when-to-use clause built from the first few
triggers: phrases ("Use for: qa test this, find bugs on site, test the
site."), or from the skill's "Use when" sentence when it has no trigger list;
--catalog-mode=full and the other hosts don't get that clause.