ship

Merge base branch, run tests, bump VERSION, update CHANGELOG, and create a PR.

Updated Mar 31, 2026

Search Tags:#changelog #versioning #merge #ship #pull-request #tests

Ready to run

npx skills add https://github.com/amanik/sailor-score-debug --skill ship-amanik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill ship-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflows automate a full lifecycle: merging the base branch, running tests, reviewing diffs, bumping VERSION, updating CHANGELOG, committing, pushing, and opening a PR. This reduces manual release toil and enforces a repeatable process.

Core Features & Use Cases

Deterministic ship flow: merges the base branch, runs tests, and prepares release artifacts.
Versioning & changelog: bumps VERSION, updates CHANGELOG, and surfaces release notes.
PR creation & provenance: commits changes, pushes, and creates a pull request on the target branch.
Proactive suggestions: recommends shipping when code is ready or deployment would be next.
Telemetry & observability: logs usage for auditing and improvement.

Quick Start

Trigger a full ship workflow on the current feature branch to merge, test, bump versions, update changelog, and open a PR.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate merging a base branch, running tests, and creating a pull request?▼

Automating a full ship workflow merges your base branch, runs tests, bumps versions, updates the changelog, and opens a PR. This deterministic process reduces manual release toil by enforcing a repeatable lifecycle from code merge to pull request creation.

How does changelog management and version bumping work during a code release?▼

Changelog management and version bumping occur automatically during the ship flow. The workflow updates the VERSION file, generates changelog entries to surface release notes, and commits these changes alongside your code before pushing to the remote repository and opening a pull request.

Can I trigger an end-to-end ship workflow on my current feature branch?▼

Yes, you can trigger an end-to-end ship workflow on your current feature branch. The process initiates a full lifecycle sequence: it merges the target base branch into your current context, executes tests, prepares release artifacts, and creates a pull request for deployment auditing.

What is the best way to ensure a deterministic and auditable release path for deploying code?▼

A deterministic and auditable release path is established by automating the entire release lifecycle. This approach sequentially merges the base branch, validates tests, updates versioning and changelogs, and logs telemetry, ensuring every deployment follows a repeatable, trackable process before opening a pull request.

Does the automated ship workflow provide guidance on when code is ready to deploy?▼

Yes, the automated ship workflow provides proactive suggestions. It evaluates your code readiness after merging and testing, recommending when to ship or proceed with deployment, which helps maintain a continuous and guided release cadence without manual monitoring.