gsd:ship
GitHub在验证通过后,自动推送分支、创建PR并触发审查,完成代码合并流程。
Trigger Scenarios
Install
npx skills add davepoon/buildwithclaude --skill gsd:ship -g -y
SKILL.md
Frontmatter
{
"name": "gsd:ship",
"description": "Create PR, run review, and prepare for merge after verification passes",
"allowed-tools": [
"Read",
"Bash",
"Grep",
"Glob",
"Write",
"AskUserQuestion"
],
"argument-hint": "[phase number or milestone, e.g., '4' or 'v1.0']"
}
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:
- Show ship status (e.g.,
## ✓ Phase N / Milestone v1.x Shipped — PR #123) with the PR URL - Emit a
## ▶ Next Upheading with the next command (/gsd:nextif there's more in the milestone,/gsd:complete-milestoneif this was the last phase) - Use
`/clear` then:before the command - Include a parenthetical: (
/clearis safe —/gsd:resume-workrestores position fromHANDOFF.jsonif 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.
</output_format>
Version History
- 502fc01 Current 2026-07-05 15:14


