ship
A complete landing pipeline: detect and merge base branch, run tests, review the diff, bump version, update changelog, commit, push, and open the PR, with gates at each stage.
Anatomy
| Parent repo | garrytan/gstack |
|---|---|
| Path | skills/ship |
| Trigger conditions | Slash command: /ship |
| Instruction format | yaml-frontmatter-md |
| Required tools | shell, git, github-cli |
| Reusability | stack-specific |
| Complexity | high |
| Ships scripts / examples / tests / boundaries | yes / yes / no / yes |
Failure modes
Assumes gstack's versioning and changelog conventions; on repos without them, stages no-op rather than fail loudly. Slash-command triggering means it protects nothing unless invoked.
Verdict
The best example of a loop packaged as a skill: ordered stages, verification per stage, and an explicit definition of done. Wants a paired auto-trigger so it cannot be forgotten.
Related skills
Blocks the agent from claiming work is complete, fixed, or passing until it has run verification commands and confirmed output. Evidence…
Forces root-cause investigation before any fix: reproduce, hypothesize one cause at a time, test the hypothesis, then patch. Bans…
Frequently asked questions
What does the ship skill do?
A complete landing pipeline: detect and merge base branch, run tests, review the diff, bump version, update changelog, commit, push, and open the PR, with gates at each stage.
When does ship trigger?
Its stated trigger: Slash command: /ship. Trigger precision is a scored reliability dimension.