canary (gstack)
- Release
Watches a release right after it goes out, comparing the new version's health signals against the old so a bad deploy is caught early and can be rolled back. It monitors AFTER the deploy, unlike preparing the change, performing the deploy, or intercepting risky commands.
A situation it fits
The deploy just finished. You want to keep an eye on whether this version is behaving worse than the last, so you can pull it if something looks off.
3 scenarios in the bank answer to canary (gstack). The rest are in the game.
Skills it gets confused with
These share a family with canary (gstack), which is another way of saying they are the ones you might reach for by mistake.
- careful (gstack)Acts as a safety net around destructive shell commands — force-pushes, recursive deletes, dropping a table — pausing to confirm before something irreversible runs. It guards individual dangerous actions, not the steps of preparing, deploying, or monitoring a release.
- land-and-deploy (gstack)Takes an approved change the rest of the way — merges it and pushes it live to production. Its job is the deploy itself, distinct from preparing the change and opening a PR, from watching how the release behaves afterward, and from guarding against destructive commands.
- ship (gstack)Runs the pre-merge release pipeline on a finished change — merges the base branch, runs the tests, reviews the diff, bumps the version and changelog, then commits and opens the pull request. It gets a change ready to land and raises the PR; it is not the act of deploying to production, watching a deploy, or blocking a dangerous command.
Knowing what canary (gstack) does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessioncanary (gstack) is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.