Ship
Use when shipping work end-to-end. Names branch, commits, pushes, creates PR — no confirmation. Triggers: ship, ship it, send it, go from uncommitted changes to open PR.From its SKILL.md
npx -y skills add neumie/almanac --skill shipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.2 KB, 747 tokens by cl100k_base, as published. Nobody here has run it
Ship
Run the full workflow: name the branch, commit, push, and open a PR. Each step runs unconditionally — the step itself decides whether to act or skip. Stop immediately if any step fails.
If the user says "ship draft" or "draft", create the PR as a draft.
Pre-run state
These commands run automatically when the skill loads — output replaces each line below:
- Working tree status: !
git status - Current branch: !
git branch --show-current - Workflow count: !
gh api repos/{owner}/{repo}/actions/workflows --jq '.total_count' 2>/dev/null || true
Step 1 — Name the branch
Follow the branch-name skill to analyze the branch contents and rename if needed.
- If the branch already has a good descriptive name (matches
<type>/<description>pattern and accurately describes the work), keep it. - Otherwise, the
branch-nameskill will rename it.
Record
Note for the summary: Branch: <name> (or Branch: <name> (kept) if unchanged).
Step 2 — Commit
Follow the commit skill to analyze changes and create commits.
If there are no staged or unstaged changes, skip this step. Record: Commit: nothing to commit (skipped).
Record
Note for the summary: Commit: "<message>" (or multiple lines if split into multiple commits).
Step 3 — Squash commits
Follow the commits-squash skill to combine related commits into logical groups. If there are 0 or 1 commits, or commits are already clean, the skill will skip automatically.
Record
Note for the summary: Squash: N commits into M (or Squash: already clean (skipped)).
Step 4 — Push
Follow the push skill to push the branch to remote safely. It will handle tracking, safety checks, and updating any open PR description.
Record
Note for the summary: Push: N commits to origin/<branch> (or Push: already up to date (skipped)). If PR was updated: PR #N: description updated.
Step 5 — Create PR
Follow the pr-create skill to create the pull request. If the user requested a draft, pass that through.
If an open PR already exists, skip creation. Record: PR: #N already exists — <url>.
Record
Note for the summary: PR: Created #N — <url> (add (draft) if applicable).
Final Summary
After all steps complete, print a compact summary:
Shipped:
Branch: feat/add-user-avatar
Commit: "feat(avatar): add upload endpoint"
Squash: 5 commits into 2
Push: 1 commit to origin/feat/add-user-avatar
PR: Created #42 — https://github.com/org/repo/pull/42
Replace any skipped steps with their skip message (e.g., Commit: nothing to commit (skipped)).
After the summary, use the workflow count from the pre-run:
- If workflows exist (count > 0): invoke the
pr-watchskill on the PR immediately — do not ask. - If no workflows (count is 0): ask "Merge?" — if yes, follow the
pr-watchskill's Merge Procedure. It detects the repository's enabled merge methods; never assume squash, merge commit, or rebase.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most ship operate skills give in 747 tokens
Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07
- Document a rollback plan before deploymentin 41 of 779, across 22 files
- Update the changelogin 21 of 779, across 19 files
- Run the test suitein 20 of 779
- Create an annotated git tagin 20 of 779
- Clean up feature flags after full rolloutin 18 of 779, across 10 files
- Verify deployment health after launchin 18 of 779, across 10 files
- Test both feature flag statesin 17 of 779, across 9 files
- Verify the working tree is cleanin 17 of 779
- Make database migrations backward-compatiblein 16 of 779, across 8 files
- Set up error monitoring before launchin 15 of 779, across 7 files
- Monitor metrics at each rollout stagein 14 of 779, across 5 files
- Create a GitHub releasein 14 of 779
Said here and by no other author read
- run the full shipping workflow
- name the branch
- squash related commits
- print a compact summary after all steps
- invoke pr-watch on the new pull request immediately
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.