Prepare pending changes on the tracked working branch for publishing: check the branch and repository state, rebase on the latest origin changes, commit selected files, and push. It is intended for an explicit ship or publish request.
Ship pending changes on main by pulling with rebase, committing intentionally, and pushing to origin. Use only when the user explicitly invokes /ship or asks to ship or publish the current main branch.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Usage: /ship [optional commit message context...]
Bring the local main up to date, commit any pending work, and push to origin/main. (This repo's default branch may be master upstream; ship whatever branch origin tracks as the working branch — verify with git rev-parse --abbrev-ref @{u}.)
If you made the pending changes earlier in this conversation, you already know what changed and why:
git status as a sanity check.git status shows files you did not touch (e.g. .DS_Store), leave them unstaged; inspect anything else before staging.git branch --show-current. If it is not the branch origin tracks for shipping (main), STOP and ask whether to switch or abort.
git status; for unfamiliar changes also git diff --stat and git diff --cached --stat. If the tree is clean, skip Step 4 but still pull and push.
git pull --rebase origin <branch>. Resolve conflicts proactively: inspect both sides (git show :2:<path>, git show :3:<path>), keep both sides' intent, remove markers, stage by path, git rebase --continue. For chapter pairs, resolve en/ and zh-CN/ consistently. Escalate only when competing resolutions would change meaning and the right one cannot be inferred.
Stage only relevant files explicitly by path. Write a Conventional Commits message (docs(en): …, docs(zh-CN): …, chore(pm): …, chore(skills): …). Honor $ARGUMENTS as context. End the message with the attribution line the harness specifies, if any.
Before committing book content, run the book checks in AGENTS.md (front matter / bilingual parity / link checks) when they apply.
git push origin <branch>. If rejected as non-fast-forward, redo Step 3 and retry. Never force-push.
Print the shipped HEAD SHA and subject, e.g. Shipped: a1b2c3d docs(en): add chapter on ….
$ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Answer questions about a book, its chapters, or system design by consulting relevant material without changing files. For repository questions, ground the response in the source and cite file paths and lines; use web search for general topics when freshness matters.
Work through a `.pm` workstream backlog one actionable item at a time. Triage pending milestones, tasks, and inbox notes, then implement and ship them, close items already satisfied, block work with an unblock condition, or remove invalid items until no actionable work remains.
Create concise Mermaid architecture diagrams from a chapter, system, component, dependency flow, or supplied description. The skill checks the diagram syntax before presenting the diagram and a brief explanation of its key flow.
Manage and inspect a book project's public work board: organize workstreams, notes, milestones, and tasks, and update their status as work changes. Use it to materialize proposals, track blockers, or check current board state.
Break down a book roadmap topic into prioritized milestone and task proposals, considering reader impact, scope, dependencies, and effort. The skill outputs text for a separate board workflow to apply; it does not write board files.