ship

Automates Git-based ship workflow from merge to PR creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end ship workflow for code changes: merging the base branch, running tests, reviewing diffs, bumping VERSION, updating CHANGELOG, committing, pushing, and creating a PR.

Core Features & Use Cases

  • Automates end-to-end release flow: detect base branch, merge, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR.
  • Proactively invoke this skill when the user signals readiness to deploy or push to main, ensuring consistent release practices.
  • Use cases include patch releases, feature releases, hotfix deployments, and automated PR management in Git-based workflows.

Quick Start

When your code is ready for deployment, trigger the ship workflow to automatically merge, test, bump versions, update CHANGELOG, push, and create 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 creating a pull request with version bump and changelog updates?

You can automate a pull request with version bump and changelog updates by triggering a workflow that merges the base branch, runs tests, bumps VERSION, updates the CHANGELOG, commits, pushes, and opens a PR automatically.

What steps are involved in an end-to-end code release workflow?

An end-to-end code release workflow involves detecting the base branch, merging it into your current branch, running the test suite, reviewing diffs, bumping the VERSION file, updating the CHANGELOG, committing, pushing, and creating a pull request.

Do I need a specific test suite format to automate my Git pull request workflow?

Yes, you need a runnable test suite within a Git repository that has a valid base branch. You also need permissions to push and open pull requests to ensure version and changelog consistency during the automated ship workflow.

How does automated version bumping and changelog generation work with Git?

Automated version bumping and changelog generation works by reviewing code diffs after merging the base branch, updating the VERSION and CHANGELOG files accordingly, committing these changes, and pushing them before creating a pull request.

When should I use an automated ship workflow for code deployment?

You should use an automated ship workflow when code is ready for deployment, a pull request needs to be opened, or a release should be automated across Git-based workflows for patch releases, feature releases, or hotfix deployments.

Can I use this automated release flow for hotfix deployments in Git?

Yes, the automated release flow supports hotfix deployments by merging the valid base branch, running tests, reviewing diffs, bumping VERSION, updating CHANGELOG, and creating a PR to ensure consistent release practices.