/rota-ship

Review, then open the PR or merge, linking items by ID.

When to use

Use on “ship it”, “open the PR”, “finish this branch”, or when work is done and ready to integrate. Use –undo on “roll back the last cycle”, “revert that merge”.

Reach for another skill when

you want a verdict only and nothing integrated: /rota-review
you are cutting a tagged version, not landing a branch: /rota-release

Usually before/rota-review/rota-work

/rota-ship

Usually after/rota-release

Exampleillustrative, condensed

/rota-ship

/rota-review: PASS
PR body built from commit subjects and resolved IDs: B03
Merged into main with --no-ff; branch deleted.

What changes

B03 under ## Completed in BACKLOG.md, stamped with the fix commit’s hash
main carries the fix as one revertable unit
status.json entry cleared

Where this example comes from

Flags and modes

--undo: guided rollback of the last cycle on the base branch; dry-run preview first, asks before applying
--docs: deprecated alias for /rota-docs

Details

Finishes a feature branch: runs /rota-review (by default), builds a PR body from commit subjects and resolved item IDs, then either opens a PR (GitHub) or MR (GitLab) or merges directly based on work.mergeStrategy. Clears the status.json entry and closes referenced items on completion. On the issue backend it always opens a PR or MR with Closes #N lines and never merges; the merge closes the issues (issue backend). See review and ship.

--undo is the one flag mode:

/rota-ship --undo: guided rollback of the last /rota-work cycle on the base branch. Resets the merge commit and restores the cycle’s TODO entries to their type sections in BACKLOG.md. Direct-merge cycles only (MVP); PR-mode cycles refused with a manual-recovery pointer. Refuses on cycles that have post-merge commits unless --allow-post-merge is passed. It defaults to a dry-run preview and always asks for explicit confirmation before applying. See rolling back a cycle for the full flow.