shiplisted

# ship Make finished work live on robertritacca.com — builds green first, no unrelated files swept in, a clear report after. The end state is always the same: the work is on `main`, pushed, and deployed. ## When invoked Use this skill when asked to make completed work live — phrases like "ship it", "make it live", "push to main", "deploy this". This skill always ends with a deploy; to save progress without deploying, that's `checkpoint` (or `park` to also return to main). **If asked to "merge and push"**: that's the retired ambiguous skill name, and it now maps onto more than one verb. Confirm the intended end state before doing anything: `ship` (merge into `main`, push, deploy), `checkpoint` (push the branch, keep working), or `land` (combine several pieces of pending work into a local `main`, pushing nothing). ## Instructions 0. **Check the branch**: `git branch --show-current`. - **On `main`**: follow steps 1–7 directly. **A push to main deploys robertritacca.com.** - **On any other branch**: the work rides the branch into `main`. Follow steps 1–4 on the branch (commit there), then merge in step 5. Never cherry-pick or copy files across branches to avoid a merge. 1. **Survey the tree before touching anything**: run `git status --short` and classify every entry: - **In scope** — files created or modified as part of the work just completed in this session - **Out of scope** — anything untracked or modified that predates the session, or that wasn't part of