shipitlisted

# shipit — land a reviewed PR > Follow `skills/progress-tracking/SKILL.md`: this procedure has more than two steps — > seed one todo item per step below before starting and mark each complete as you go. `shipit` lands a pull request that already passed review. It pushes any unpushed local commits, waits for CI to go green, and squash-merges. The PR title then lands as the commit subject on the base branch. If a project puts a version in the title, that version shows up in `git log`. It **finalizes an existing open PR**, and never opens one. It is generic, and it does no versioning, changelog editing, or release work. If a project assigns a version at land time, that happens in a separate project-specific step *before* `/shipit` (in this repo, the dev `version-bump` skill — see [docs/versioning.md](../../docs/versioning.md)). `shipit` only cares that the branch is ready to land. `gh pr merge` is irreversible, so two things guard it — neither of them a frontmatter flag, and neither of them a question put to the user mid-run: 1. **Explicit ship intent.** The skill fires only on a direct "ship it" / "land the PR" / `/shipit`. An approved, green, or finished-looking PR is *not* ship intent — the user decides when to land. 2. **CI green** (step 3), which gates the merge mechanically — a red or timed out check stops the land before `gh pr merge` ever runs. **Do not ask the user to confirm the merge.** Ship intent already carried the authorization to merge, so a confirm