ship-upgrade

Detect install type, back up, upgrade Ship, and summarize CHANGELOG.md updates.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shaneholloman/ship --skill ship-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-upgrade
Source: https://github.com/shaneholloman/ship/tree/main/ship-upgrade
Command: npx skills add https://github.com/shaneholloman/ship --skill ship-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading Ship to the latest version can be complex due to different install types (global vs vendored). This guide explains how the upgrade flow detects install type, backs up current state, applies the upgrade, and surfaces what changed.

Core Features & Use Cases

  • Detects install type (global-git, local-git, vendored, vendored-global) and upgrades the correct copy.
  • Performs safe upgrades with backups and rollback if setup fails.
  • Summarizes What's New from the primary install's CHANGELOG and shows it to the user.

Quick Start

Run /ship-upgrade to begin the upgrade flow and upgrade Ship to the latest version.

Frequently Asked Questions about ship-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade ship to the latest version automatically?

To upgrade ship automatically, run the upgrade flow to detect your installation type, back up the current state, apply the version update, and extract changelog summaries from CHANGELOG.md to show what is new.

How does ship handle version upgrades for both global and vendored installations?

Ship version upgrades detect the specific install type—whether global-git, local-git, vendored, or vendored-global—and applies the upgrade to the correct copy while backing up the current state for rollback safety.

What is the safest way to update a vendored ship installation without breaking setup?

The safest way to update a vendored ship installation is using an automated upgrade path that creates a backup first and performs a rollback if the setup fails, ensuring your environment remains stable.

Can I see what changed in a ship version upgrade before finalizing the update?

Yes, the ship upgrade process extracts and summarizes 'What's New' directly from the primary installation's CHANGELOG.md, presenting user-facing updates so you can review changes immediately after upgrading.

Why does my ship upgrade fail when I have both global and local copies installed?

Ship upgrades can fail with mixed installations if the wrong copy is targeted, so the upgrade flow detects whether your environment uses global-git, local-git, or vendored setups to upgrade the correct version.

Does the ship upgrade flow support rollback if the new version breaks my environment?

Yes, the ship upgrade flow performs safe upgrades with backups and automatically triggers a rollback if the setup fails, restoring your previous environment state from the backup.