Dw Ship

dw-ship — merge, clean up, sync

One decision, the squash — and it takes no arguments. Everything before it happened at dw-land, everything after is teardown; the merge being the closing sequence's single one-way door is the whole reason this is a second command.

What it reads

The branch state, the PR's checks, and ## Git conventions for the default branch and push rules — every git mechanic here is done the way dw-git does it. This skill writes no .ai/ artifact: its output is a merged PR, a removed worktree, and a .ai/work/ folder that stays deleted.

Workflow

1. Preconditions

• Clean tree (git status --porcelain) — leftover work gets committed the way dw-git does, or

deliberately stashed; never shipped around.

• Landed first, and that is a refusal. If a CHANGE.md still matches this branch (the same grep

dw-next uses), the change isn't closed: say so, say /dw-land, and stop. Don't offer to run the closing pass here and don't promise to pick this up afterwards — dw-land ends with the PR this skill needs, so the next dw-ship starts from a state that exists.

2. Pick the path

• Already on the default branch (resolved the way dw-git does) and it isn't protected → **fast

path: plain git push is the whole ship — no PR, no worktree. It is irreversible, with nothing between it and the default branch, and here the push really is this change's first CI**, because a push to the default branch is a trigger where a push to a feature branch is not: where dw-land left a result pending on the push, watch that run rather than calling the ship done at the push. If the change skipped dw-check, offer it first — a nudge, not a gate.

• On any other branch → the merge below.
• No origin at all → say so and offer the local ending instead: switch to the default branch,

merge, delete the branch. Never pretend to have pushed.

3. Merge the PR

1. Read the checks first: gh pr checks. Opening the PR at dw-land is what started this

change's first CI, so this is where a result the verdict recorded as pending on the push gets settled. A pending or failing check is a reason to wait and say so, not a footnote under the go.

1. gh pr merge --squash --subject "" — --subject, not --title, which

gh pr merge does not have and dies on. Pin it either way: the squash subject is what lands on the default branch forever, and left to itself it comes out as whichever commit subject GitHub picks rather than the conventional-commits subject dw-git composed.

1. No PR on the branch → dw-land never ran or its PR was closed. Stop and say which, rather than

opening one here.

4. Clean up

When the branch lives in a worktree, leave it first (the ExitWorktree tool where the session offers it, else cd to the main tree), then:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/worktree.sh" remove 

removes the worktree, deletes its branch — whatever the spelling, ` or worktree- — and prunes. For a plain feature branch with no worktree: git switch , git branch -D `.

5. Sync, then sweep what the squash brought back

git pull on the default branch, so the main tree sees the squash. Then look for its residue: a .ai/work// whose twin already sits in .ai/archive//. A shaping commit still local-only when its PR squashed is replayed on top of the squash by the rebase, re-creating that change's CHANGE.md at its shaping-time state — branch: unclaimed, status: shaping — for a change that landed minutes ago, which dw-next then offers as fresh work. Twice cleaned up by hand before this step existed: 73e003a, 9eef63d.

git rm -r every such folder — matched on the archive twin, never on the slug just shipped, since one shaping commit can carry several changes and the rest are live work. Commit on the default branch and push, confirming that push the way dw-git does. Nothing is lost: the landed copy is in the archive, and a sibling doc the same commit carried rides along untouched.

6. Report

What merged and where, what was torn down, and what the sweep removed. If landing parked follow-ups in .ai/backlog/, the next dw-shape reads them — that's the loop closing.

Next: dw-shape for the next change — the backlog is where it starts.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: dominikwozniak
• Source: dominikwozniak/dw-solo-skills
• License: MIT

Install and usage instructions live in the source repository linked above.