shiplisted

# Ship ## What this skill is — and isn't | Skill | Question it answers | Output | |---|---|---| | `vd:cook` | "Execute the plan." | Code, tests, plan status | | **`vd:ship`** | **"The branch is ready — land it."** | **Merged target, version bump, PR URL** | Ship **lands** a branch. It does not implement features and does not redesign on the fly. If tests fail or review surfaces a real bug, **stop** and kick back to `vd:cook` — don't paper over issues to keep the pipeline moving. ## Ship modes | Mode | Target branch (auto-detected) | Use for | |------|-------------------------------|---------| | `official` | `main` / `master` | Production code merge | | `staging` | `staging` / `uat` / `release/x.y.z` | Pre-prod, QA validation | | `beta` | `dev` / `development` / `beta` | Active dev / preview | Add `--release` to any mode to also cut a GitHub release. Tag style adapts to the mode: | Mode + `--release` | Tag | GitHub release | |--------------------|-----|----------------| | `official --release` | `vX.Y.Z` | Stable (latest) | | `staging --release` | `vX.Y.Z-rc.N` | Prerelease | | `beta --release` | `vX.Y.Z-beta.N` | Prerelease | If an auto-release tool is detected (`goreleaser`, `release-please`, `semantic-release`, `changesets`), Step 13 skips the manual tag and lets CI cut it. Otherwise, the user is asked for the bump level. ## Arguments | Flag | Effect | |------|--------| | `official` | Target default branch (main/master). Full pipeline incl. docs + journal | | `stag