From gsd
Pushes git branch, creates PR with auto-generated body, triggers review, tracks merge after /gsd:verify-work passes in GSD workflow.
npx claudepluginhub jnuyens/gsd-plugin --plugin gsdThis skill is limited to using the following tools:
<objective>
Automates code shipping: commits changes, pushes branch, creates/updates PR, monitors GitHub CI/CD checks, fixes failures/review comments/conflicts until merge-ready.
Finishes Git development branches end-to-end: verifies working tree/tests/lint, reviews diffs, picks merge/PR/squash/stacked strategy, writes messages, pushes, cleans up. Use when ready to ship.
Automates code shipping: merges base branch, runs detected tests, performs multi-review with auto-fixes, commits, pushes, creates PR. Use /ship or say 'ship it'.
Share bugs, ideas, or general feedback.
Closes the plan → execute → verify → ship loop.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/ship.md </execution_context>
Execute the ship workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/ship.md end-to-end.
<output_format>
When the ship workflow concludes (PR created and tracked), emit a Next Up continuation block following the pattern in references/continuation-format.md:
## ✓ Phase N / Milestone v1.x Shipped — PR #123) with the PR URL## ▶ 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)`/clear` then: before the command/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)/gsd:review (cross-AI review) or PR-specific actionsPR 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.
</output_format>