Skip to content
Back to skills

Ship

ASecurity

Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.

  • 1,531 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agents

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add hashgraph-online/awesome-codex-plugins --skill ship --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ship?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ship
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hashgraph-online-ship-awesome-codex-plugins/badge)](https://www.skillsdirectory.com/skills/hashgraph-online-ship-awesome-codex-plugins)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ship
description: Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
---
# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.