ship

Automate end-to-end shipping with merging, testing, version bumps, and PR creation.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/alexandervashurin/semaphore --skill ship-alexandervashurin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/alexandervashurin/semaphore/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/alexandervashurin/semaphore --skill ship-alexandervashurin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation reduces manual steps, speeds up releases, and ensures consistency across merging, testing, and PR creation.

Core Features & Use Cases

  • End-to-end shipping: detect base branch, merge, run tests, bump versions, update changelog, commit, push, and open PR.
  • Safeguards: handles merge conflicts, runs tests, and enforces release hygiene with automated PR reviews.
  • Use Case: When a feature is ready, invoke Ship to push a clean, auditable PR with an updated CHANGELOG and version bump.

Quick Start

Invoke Ship to perform the full automated ship workflow and open a PR URL.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git pull request creation with version bumps and changelog updates?

You can automate pull request creation, version bumps, and changelog updates by invoking an end-to-end shipping workflow that detects the base branch, merges, runs tests, commits, and opens an auditable PR.

What is the best way to handle merge conflicts during a release workflow?

Handling merge conflicts during a release workflow is managed automatically by the shipping automation, which detects issues, enforces release hygiene, and ensures a clean merge before opening a pull request.

Can I run tests before opening a pull request for a feature branch?

Yes, you can run tests before opening a pull request for a feature branch. The shipping workflow integrates with CI to execute tests, bump versions, and update the changelog prior to pushing the commit.

Does this end-to-end shipping automation work with existing CI-CD pipelines?

This end-to-end shipping automation integrates with existing CI-CD pipelines, git, and changelog tooling to enforce release governance, ensure consistent deployments, and produce traceable pull requests across feature branches and release streams.

When should I use an automated shipping workflow for release governance?

You should use an automated shipping workflow for release governance when a feature is ready, reducing manual steps, speeding up releases, and ensuring consistency across merging, testing, and PR creation.

How do I ensure consistent deployments across feature branches and release streams?

To ensure consistent deployments across feature branches and release streams, the shipping automation coordinates merging, testing, version bumps, and changelog updates to produce auditable PRs and enforce release hygiene.