Skip to main content
Generaldavepoon

gsd:ship

Create PR, run review, and prepare for merge after verification passes

Stars
2,987
Source
davepoon/buildwithclaude
Updated
2026-05-26
Slug
davepoon--buildwithclaude--ship
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/davepoon/buildwithclaude/HEAD/plugins/gsd/skills/ship/SKILL.md -o .claude/skills/ship.md

Drops the SKILL.md into .claude/skills/ship.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Bridge local completion → merged PR. After /gsd:verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.

Closes the plan → execute → verify → ship loop.

@${CLAUDE_PLUGIN_ROOT}/workflows/ship.md

Execute the ship workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/ship.md end-to-end.

When the ship workflow concludes (PR created and tracked), emit a Next Up continuation block following the pattern in `references/continuation-format.md`:
  • Show ship status (e.g., ## ✓ Phase N / Milestone v1.x Shipped — PR #123) with the PR URL
  • Emit a ## ▶ Next Up heading with the next command (/gsd:next if there's more in the milestone, /gsd:complete-milestone if this was the last phase)
  • Use `/clear` then: before the command
  • Include a parenthetical: (/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)
  • Add an "Also available:" section with /gsd:review (cross-AI review) or PR-specific actions

PR creation is a clean boundary — review/merge happens out-of-band; the just-finished implementation conversation rarely informs the next phase. Suggesting /clear here keeps the next start small.