ship

Automate feature branch shipping with merges, tests, version bumps, and PR creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end ship process for feature branches: merging main, running tests, reviewing diffs, bumping versions, updating CHANGELOG, and creating PRs.

Core Features & Use Cases

  • Non-interactive, deterministic release flow that handles pre-flight checks, merges, test orchestration, and PR creation.
  • Automatic handling of routine conflicts and consistent version bumps to keep releases reproducible.
  • Use Case: When releasing a new feature branch, run the ship workflow to produce a PR with updated changelog and version.

Quick Start

Run the /ship command on your feature branch to execute the fully automated ship workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git workflow for creating a pull request from a feature branch?

Automating the git workflow involves merging main into your feature branch, running tests, bumping versions, updating the CHANGELOG, and creating a pull request. This process handles pre-flight checks and commit hygiene non-interactively.

What is a non-interactive ship workflow for CI environments?

A non-interactive ship workflow is a deterministic release process for CI environments that automates merging main, resolving routine conflicts, orchestrating tests, and publishing pull requests without requiring manual intervention.

Can I automate CHANGELOG generation and version bumps during a pull request release?

Yes, you can automate CHANGELOG generation and version bumps. The workflow reviews branch diffs and automatically applies consistent version bumps to ensure releases remain reproducible before creating the pull request.

How does automated conflict resolution work when merging main into a feature branch?

Automated conflict resolution handles routine conflicts when merging main into a feature branch. It operates during pre-flight checks, ensuring the branch is ready for a pull request while providing clear failure signals for unresolvable issues.

Do I need any specific dependencies to run an automated end-to-end ship process?

No specific dependencies are required to run the automated end-to-end ship process. It is designed to work within Git-based release workflows to produce PR-ready code with integrated safety checks.