ship-it
Ship It
Overview
Use this skill to send work all the way into production and check on it — promote per repo policy, then verify the deploy and observe that production is healthy. This is not “merge a PR into the next integrate target” (merge-it).
This is commonly staging -> main for deployed applications, but the branch path is repo-level policy, not a global default. Libraries, SDKs, CLIs, crates, packages, and local tools often release from feature branches directly to the default branch or through a separate tag/package flow; do not force a staging promotion path onto those repos.
When the user wants to land work on staging only (not production), use stage-it instead. When the user wants to merge current work into its next integrate target (main, release branch, staging, etc.), use merge-it instead.
This skill does not mutate production data, seed CMS records, rotate secrets, or bypass branch protection unless the user explicitly asks for a separate operational change and the repo runbook allows it.