ship
Installation
SKILL.md
Ship the current changes as a merged PR.
Read shared/git.md first.
Step 0 inspects the repo and prints an execution plan that marks each downstream step as RUN or SKIP. Follow that plan exactly — do not run a SKIP step, do not invent new ones. If any step exhausts its retry budget, stop and ask the user.
Common paths
- On base branch with changes → branch off → (test) → commit → PR → CI → merge → (worktree cleanup).
- On feature branch with open PR → (test) → (commit) → push → CI → merge.
- Clean tree, on base, no open PR → early-exit at step 0; nothing to ship.