Ship Preflight

Run the repository-defined full verification suite before declaring a slice done, pushing it, or issuing a deploy command. This is a one-shot gate, not a loop.

Steps

1. Read the repository instructions and current Git state. Preserve unrelated changes and identify the canonical full-check command.
2. Run that canonical command once. If no aggregate gate exists, run the documented checks in strict order:
   • typecheck — must exit 0
   • tests — ALL must pass (no skips, no flakes tolerated)
   • build — must produce a clean artifact
   • lint / size gate — if configured
3. If any gate is red: stop immediately, name the gate that failed, and report the error. Do not continue.
4. If all gates pass, distinguish the authorized effect:
   • Routine branch push explicitly authorized: verify the intended commit, branch, and remote relation, then push only that branch. A push does not authorize a release, tag, deploy, or unrelated commit.
   • Deploy, publish, notarize, release, or release tag not explicitly authorized: print the exact command and stop.

Constraints

• On kernel/host changes, run the FULL suite — not a subset.
• Never skip a gate to unblock a deploy.
• Never deploy, publish, notarize, release, or push a release tag without exact authorization.
• Never stage or commit unrelated work to make a tree appear clean.
• A dropped tool connection counts as "gate incomplete" — re-run, don't assume pass.

Report format

Gate results:
  typecheck  — PASS | FAIL (<error summary>)
  tests      — PASS (<n> passed) | FAIL (<n> failed, <first failure>)
  build      — PASS | FAIL
  lint       — PASS | FAIL (<violation count>)

Overall: GREEN — ready to ship | RED — blocked on <gate>
Next step: <deploy command or "fix <gate> first">

Usage

Run it as a one-shot before any slice completion claim:

Run /ship-preflight before marking this done.

Or as a pre-commit hook or pre-deploy check in a loop:

After building the card, run /ship-preflight. Only move it to shipped if all gates pass.