Ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack)

138,407 stars 20,523 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add garrytan/gstack --skill ship
Manual install
git clone --depth 1 https://github.com/garrytan/gstack.git /tmp/gstack
mkdir -p ~/.claude/skills
cp -r /tmp/gstack/ship ~/.claude/skills/ship

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Shared preamble (load first)

This skill follows gstack shared preamble `4e82fa4c839f` (AskUserQuestion format, voice, writing, completeness and completion rules). If your Read of that file, headed by this id, is still in context, do not read it again; otherwise Read `~/.claude/skills/gstack/ship/sections/preamble.md` in full before the command below. A section or subsection here with a shared heading replaces the shared one.

## Preamble (run first)

```bash
~/.claude/skills/gstack/bin/gstack-skill-start --skill "ship" --model "claude"
```

Read the echoed `KEY: value` STATUS lines — they drive every preamble rule
below. **Degraded mode:** if `SKILL_START_PROTO: 1` is missing from the output
(script absent, stale install, or a different protocol number), apply safe
defaults: treat `SESSION_KIND` as `interactive`, do NOT assume Conductor,
skip onboarding/telemetry steps (their gates are marker-based, so consent and
onboarding prompts are DEFERRED to the next healthy run — never lost), tell
the user to run `./setup` or `/gstack-upgrade`, and proceed with their task.
Note `SESSION_ID` and `TEL_START` from the output — the Telemetry step needs
them at skill end.

**Instruction blocks:** the output may contain
`GSTACK_INSTRUCTION_BEGIN: <id> <session-id>` … `GSTACK_INSTRUCTION_END`
blocks — one-time onboarding and consent directives whose runtime gates fired.
Follow each before continuing, then proceed with the user's task. Honor a
Read the full skill on GitHub

Details

Skill name
ship
Path
ship/SKILL.md
License
MIT
Repo updated
31 October 2026

FAQ

What does the Ship skill do?

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack)

How do I install the Ship skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add garrytan/gstack --skill ship. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ship popular?

It lives in garrytan/gstack, which has 138,407 GitHub stars and 20,523 forks, and is included in 2 curated skill lists.

Related skills

Design Review

138k

garrytan/gstack

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)

Testing & QAIn 2 lists21k

QA

138k

garrytan/gstack

Fix browser/API/CLI/job/worker/webhook bugs. (gstack)

Testing & QAIn 2 lists21k

Benchmark

294k

affaan-m/ECC

このスキルを使用して、パフォーマンスベースラインを測定し、PR前後の回帰を検出し、スタック代替案を比較します。

Git & Code ReviewIn 1 list43k

Git Guardrails Claude Code

308k

mattpocock/skills

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

Git & Code ReviewIn 1 list26k

Blueprint

294k

affaan-m/ECC

1行の目的を複数セッション、複数エージェントエンジニアリングプロジェクト向けのステップバイステップ構築計画に変換します。各ステップには自己完結型コンテキストブリーフがあり、新しいエージェントがそれをコールドで実行できます。 敵対的なレビューゲート、依存グラフ、平行ステップ検出、アンチパターンカタログ、計画変更プロトコルを含みます。 トリガー:ユーザーが複雑なマルチPRタスク用の計画、ブループリント、またはロードマップをリクエストするか、複数のセッションが必要な作業を説明する場合。 トリガーしない場合:タスクが単一のPRまたは3未満のツール呼び出しで完成可能な場合、またはユーザーが「単にやってくれ」と言う場合。

Git & Code ReviewIn 1 list43k

Code Review

308k

mattpocock/skills

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Git & Code ReviewIn 1 list26k

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.