ship

Automates release publishing by drafting a CHANGELOG section and running a versioned bump, tag, build, and deploy script.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill ship-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill ship-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a new version of the project involves many error-prone manual steps: drafting changelog entries, bumping the version, committing, tagging, pushing, building, and deploying to gh-pages. This Skill condenses the entire release into one judgment step plus one script invocation, with built-in guards against half-finished releases. ## Core Features & Use Cases - CHANGELOG drafting: Computes the new version from package.json and the argument (patch, minor, or explicit x.y.z), then inserts a newest-first Added/Changed/Fixed section in the project's house voice. - One-script release pipeline: Runs src/scripts/ship.sh to bump the version, create a pathspec release commit, tag vX.Y.Z, push main and the tag, build in an isolated worktree, strip DEV code, and deploy to gh-pages. - Resumable and guarded: The script refuses to release without a CHANGELOG section, skips steps that already exist, detects half-finished runs via missing version tags, and offers a bounded --verify-live check. - Use Case: After merging a batch of features, invoke the skill with a minor bump to draft the release notes and publish version 0.4.0 to production in about 30 seconds. ## Quick Start Ask the assistant to ship a patch release, and it will draft the CHANGELOG section and run the ship script to bump, tag, build, and deploy.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I release a new version with the ship skill?

Invoke the skill with an optional version argument: patch (default), minor, or an explicit x.y.z. It drafts the CHANGELOG section first, then runs bash src/scripts/ship.sh with the same argument to bump, commit, tag, push, build, and deploy.

How do I verify the release is live after deploying?

Run bash src/scripts/ship.sh --verify-live for a single bounded check of the deployed site. It performs one verification pass and never loops, so it is safe to run after the deploy step completes.

What happens if a previous release run failed halfway?

The skill detects half-finished runs: if package.json has a version with no matching v tag, that version is treated as current and is not re-bumped. Re-running ship.sh is safe because each step skips work that already exists.

Can the ship skill be triggered automatically by the AI?

No. The skill is user-invoked only, with disable-model-invocation set and explicit rules against agent-initiated invocation or running ship.sh autonomously. A human must request the release each time.

Why does the release script refuse to run sometimes?

The script refuses to release when the CHANGELOG section for the new version is missing. Draft the Added/Changed/Fixed entries first, then re-run the script; the pre-push verify step also acts as the release gate.