ship · git:20261028.c337758 · 2026-10-28 · sha256 7f5242763bc4cd40

ship git:20261028.c337758A

Immutable. This exact content never changes and is served at /api/v1/blob/7f5242763bc4cd40.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_s5wnrmyrrnimpxex/7f5242763bc4cd403d5aef432f8a481e245707587a7e1cf5e1e788e53aaa86a2.json

Then /plugin install ship@markdownregistry-s5wnrmyrrnimpxex in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: ship
description: Use when the user says "/ship", "ship it", "commit and push", "is it committed", or at the end of a work chunk that touched a repo. Commits, pushes and reports proof in one pass.
---

# /ship: commit, push, prove

1. Target: no argument means the vault (`$ECX_VAULT`); an argument names a project repo.
2. `git status --short`. If clean: "nothing to ship" plus the last commit hash, then stop.
3. Code repos: never commit to main/master. Create or switch to a feature branch first. (Your notes vault may commit to its default branch.)
4. Split into logical commits by topic (2 to 5 is typical). Conventional messages: `feat:`, `fix:`, `notes:`, `content:`.
5. Push the current branch.
6. Report proof in exactly this shape:

```
Shipped: <n> commits pushed to <branch>
<hash> <message>
<hash> <message>
```

If the push fails, show the real error. Never say shipped when it isn't.