---
name: hashgraph-online-ship
description: "Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish."
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "ef88596a-0b55-4826-9e83-c824623160ba"
  decimalai-version-id: "8cdd2223-4031-4f4a-b80a-89324ad23531"
  decimalai-version: "3"
  decimalai-body-sha256: "b7b7dcae939f880913086cb6acb2c53ac8dbac806300823f5613a5ec3d1a8d4b"
  decimalai-name: "hashgraph-online/ship"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "devops"
  decimalai-source: "https://app.decimal.ai/s/hashgraph-online-ship@3/SKILL.md"
---
# Ship

If `topology=multi-module` (triage announcement or coordinator spec/plan declaration), read `../references/multi-module.md`.

**Gates — if any fail, stop here:**

- Tests pass — or, for tasks with no automated test, their manual acceptance was performed.
- No `- [ ]` remains in any relevant plan.
- Staging spec reflects actual code behavior.
- README commands runnable; living docs honor North Star (atemporal ground truth, modular specs; see `../references/quality.md`).
- No incomplete tracked tasks in the harness task tracker (whatever the host calls it).
- For multi-module work: module plans and local acceptance are complete, and coordinator integration passes (or the change is reported as `partial-commit`).

1. `review` the whole diff.

2. **Update `docs/ROADMAP.md`** (if it exists):
   - Milestone completed? Mark `[x]`.
   - Scope changed? Adjust upcoming milestone descriptions.
   - Unrelated work (bugfix, refactor)? Roadmap unchanged.

3. `archive` — for multi-module work, archive module artifacts in their owning repositories first; archive the coordinator last.

4. If user-visible, add to CHANGELOG `Unreleased`. Releases move it to a version.

5. Ask disposition: **commit / merge / PR / keep / discard.**  
   For a linked multi-repository implementation whose approved plan already includes linked commits: run the commit protocol (non-coordinators in dependency order, record SHAs as the revision set, coordinator last, shared change-set ID in every commit) when the user chooses **commit** or previously approved that path — do not re-ask whether commits are in scope. Still never push or open a PR without explicit approval.

If a linked commit fails, report `partial-commit`, preserve all commits and working trees, and report the exact recovery point.

6. On merge or PR: clean up worktree, delete local branch.

7. Roadmap has unchecked milestones? → `plan` next.

No push or PR without explicit user approval.