ship

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

Updated Mar 22, 2026

Search Tags:#automation #git #release #ci-cd #ship #pull-request

Ready to run

npx skills add https://github.com/jeisenback/original-curse-killer --skill ship-jeisenback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill ship-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping software often requires a sequence of manual steps: aligning the feature branch with the base, running tests, updating version metadata and changelogs, committing changes, and opening a PR. This skill automates those steps to reduce toil and ensure consistent releases.

Core Features & Use Cases

Detects the base branch, merges it into the feature branch, and runs the project's test suite to validate changes.
Bumps versions, updates CHANGELOGs, commits, pushes, and creates a pull request automatically.
Suitable for CI/CD pipelines and release automation across multiple projects requiring deterministic shipping workflows.

Quick Start

Use the ship skill to automatically prepare a release PR from your feature branch to the base branch.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate a release workflow from a feature branch to main?▼

Automating a release workflow involves merging the base branch into your feature branch, running tests, bumping versions, updating the CHANGELOG, and creating a pull request. This skill executes that deterministic shipping process end-to-end.

What is the best way to ensure consistent CI/CD releases across multiple projects?▼

Consistent CI/CD releases across multiple projects require a deterministic ship process that automatically aligns branches, validates tests, updates version metadata, and opens pull requests without manual intervention.

Do I need Git access and a configured remote to automate pull request creation?▼

Yes, automating pull request creation requires Git access, a configured remote, and a working environment capable of pushing commits. Appropriate test commands must also be configured to validate changes before shipping.

Can I automatically bump versions and update changelogs before opening a PR?▼

Yes, you can automatically bump versions and update CHANGELOGs before opening a PR. The automation sequences these steps together with branch merging and test validation to prepare a complete release pull request.

Does automated branch merging run my project's test suite before shipping?▼

Yes, automated branch merging runs your project's configured test suite to validate changes after merging the base branch into the feature branch, ensuring code stability before version bumping and pull request creation.