ship

Automate merging, testing, version bumps, changelog updates, and PR creation for software releases.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/benrapport/Vote-Better --skill ship-benrapport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/benrapport/Vote-Better --skill ship-benrapport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the final deployment workflow by handling merging, test runs, version bumps, changelog updates, commits, and PR creation when code is ready to ship.

Core Features & Use Cases

  • Automatic merge to the base branch, followed by test execution and diff review.
  • Version bump and CHANGELOG update to reflect changes.
  • Create and push PRs for deployment with minimal manual steps.

Quick Start

Trigger the ship workflow on a ready branch to automatically merge, test, bump version, update changelog, commit, push, 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 my git release workflow from merge to pull request?

Automate your git release workflow by triggering the ship process on a ready branch to handle merging, test execution, version bumps, changelog updates, and pull request creation with minimal manual steps.

Can I automatically update my changelog and version number during CI/CD?

Yes, you can update your changelog and version number during CI/CD by triggering an automated ship workflow that executes test runs, applies version bumps, updates the CHANGELOG, commits changes, and pushes them before creating a PR.

What is the best way to ensure a branch is ready before creating a deployment pull request?

The best way to ensure a branch is ready for a deployment pull request is using an automated ship workflow that enforces base-branch checks and orchestrates test execution before applying version bumps, changelog updates, and final PR creation.

Does this automated pull request workflow require any external dependencies?

No external dependencies are required for this automated pull request workflow. It uses your existing CI/CD and git tooling to orchestrate end-to-end merging, testing, versioning, changelog management, and PR publishing without extra components.

What happens if my tests fail during the automated version bump and merge process?

The automated version bump and merge process orchestrates test execution after merging to the base branch. If tests fail during this workflow, the process halts before committing changes, updating the changelog, or creating the final deployment pull request.