---
name: ship-it
description: Use when user sends a terse landing command — "push", "push deploy", "commit and push", "ship it", "land this", "clean up the worktree and branch", "wrap up" — and expects the full gate→commit→land→deploy→cleanup chain without spelling it out. Runs verification gates, commits, lands per project rule, deploys where push=deploy, cleans worktrees.
---

# Ship-It — Terse Landing Command → Full Chain

Audience: AI coding agents first.

MUST follow `/home/user/Projects/0 DOCS/GIT_FATIGUE.md` §12. Delivery controller owns validation, publication, deploy, and cleanup. Agents MUST NOT run raw publication commands or surface git/CI decisions or noise.

"push" from user = request delivery-controller completion, not `git push`.

## Chain (ordered; a failed link BLOCKS the rest — fix or report, never skip)

1. **Gate**: read valid receipt/log for current tree. No valid receipt → designated executor runs one canonical gate. NEVER rerun broad typecheck/build/test to verify. Mass failures → capture once, cluster, repair ALL, ONE replacement run. Minimal failing regression test during TDD is allowed.
2. **Commit**: local, caveman:ultra one-sentence message, Conventional Commits. NEVER co-author. Verify HEAD is YOUR commit before any `--amend` (concurrent-writer footgun).
3. **Land**: call project delivery controller. Internal PR/branch/merge mechanism is controller-owned; NEVER ask owner or run raw publication commands.
4. **Deploy** (only when requested): controller deploys verified candidate and records live probe receipt. Cloudflare implementation → `cloudflareops` skill.
5. **Cleanup**: remove worktree + delete merged branch ONLY for branches this chain landed. DO NOT prune other in-flight worktrees.

## Report

One final message MUST be `Preview ready` with inspection target + expected result, or `Needs product decision` with one concrete product decision + impact. Keep receipts and operational detail in controller log.

## Boundaries

- User said "commit" only → steps 1–2, stop. "push" → 1–3. "push deploy" → 1–5.
- MUST read `GIT_FATIGUE.md` §12 before adding any gate, hook, CI step, or ceremony.
