Installs into .claude/skills of the current project.
Are you the author of Garrytan Gstack Ship?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/nota-america-garrytan-gstack-ship-forgecat-agent-profiles)
---
name: ship
description: 'Ship workflow: detect + merge base branch, run tests, review diff, bump
VERSION,
update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy",
"push to main", "create a PR", "merge and push", or "get it deployed".
Proactively invoke this skill (do NOT push/PR directly) when the user says code
is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)'
---
# ship
Resolve `scripts/entry.py` relative to this SKILL.md, then invoke it by absolute path:
Set `SKILL_DIR` to the absolute directory containing this file, as supplied by skill discovery.
```sh
python3 "$SKILL_DIR/scripts/entry.py" instructions --host codex --skill ship
```
Use `claude-code`, `cursor`, `codex`, `openclaw`, or `hermes` for the current platform.
Follow the returned runtime contract and read the complete referenced workflow before acting.
Repeat the returned environment prefix on each shell call; variables do not persist between tool calls.
If setup is missing, explain the exact preparation command and obtain consent before downloads or builds.
Never silently use another gstack installation. Preserve the source workflow's questions and permission boundaries.
