ship

Automates atomic git commits, version bumps, changelog updates, and CI-monitored releases.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Suge8/skills --skill ship-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Suge8/skills/tree/main/development/ship
Command: npx skills add https://github.com/Suge8/skills --skill ship-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a messy working tree into clean commits, versioned releases, and green CI runs is repetitive and error-prone. This Skill standardizes the entire ship workflow—commit splitting, version bumping, changelog writing, tagging, and CI monitoring—while learning each repository's own conventions instead of imposing hardcoded rules. ## Core Features & Use Cases - Atomic Commit Splitting: Groups working-tree changes into fine-grained, single-intent commits that can be independently reverted or bisected, matching the repo's existing commit style (emoji prefixes, conventional commits, scope conventions). - Release Management: Bumps semver versions, updates CHANGELOG entries (including bilingual changelogs), creates release commits and tags in the correct order, and pushes them. - Secret Scanning & CI Watch: Scans diffs for leaked keys, tokens, and internal addresses before committing, then watches CI runs to green and reports release artifact links. - Use Case: You finished a feature plus a small fix and docs update. Say "ship it" and the Skill splits the work into separate feat/fix/test/docs commits, bumps the version, updates the changelog, tags the release, and confirms CI passes. ## Quick Start Tell the agent to ship the current working tree changes and update the version and changelog.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I split large git changes into atomic commits?▼

Group changes by logical unit using git add -p or per-file staging, giving each commit a single intent that can be independently reverted. The test is whether reverting any one commit leaves the others still valid.

How to automate version bump and changelog before a release?▼

Determine the new semver version from the changes, update version files like package.json or Cargo.toml, and generate changelog entries from the commits in user-facing language. Commit this as a release commit, then tag and push.

Does this skill modify code during the release process?▼

No. It never changes business code during shipping; lint auto-fixes are the only exception. Code problems discovered during the process are reported to the user rather than fixed inline.

What happens if CI fails after pushing a release tag?▼

The skill watches CI with gh run watch until green. If a run fails, it analyzes the logs, fixes issues caused by the current release and reruns the flow, or reports pre-existing failures to the user.

How are leaked secrets handled before committing?▼

A desensitization scan checks the diff for keys, tokens, internal addresses, and personal path patterns before any commit. If a match is found, the process stops immediately and reports the finding to the user.