ship

Automate release workflows by merging branches, running tests, and creating PRs.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cheng80/rummipoker --skill ship-cheng80
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/cheng80/rummipoker/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/cheng80/rummipoker --skill ship-cheng80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow by handling merge, testing, version bumps, changelog updates, commits, and PR creation.

Core Features & Use Cases

  • Detect and merge the base branch to prepare a release.
  • Run the test suite and review diffs before shipping.
  • Bump VERSION, update CHANGELOG, commit, push, and create a PR.
  • Proactively assist when deployment or release is requested.

Quick Start

Say "ship" or "deploy" when you're ready to release and the skill will orchestrate the workflow.

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 merging to PR creation?

Automate your git release workflow by using a tool that detects the base branch, merges it, runs tests, bumps VERSION, updates the CHANGELOG, commits, pushes, and creates a PR. This handles the entire end-to-end release process automatically.

What is the best way to update CHANGELOG and bump VERSION before deploying?

The best way to update CHANGELOG and bump VERSION before deploying is to automate the process within your release workflow. A dedicated tool can review diffs, apply the version bump, generate changelog entries, and commit the changes directly.

Does the automated release process run tests before pushing the commit?

Yes, the automated release process runs your test suite and reviews diffs before pushing the commit. It ensures the merged base branch passes testing prior to bumping the VERSION and creating a PR.

How do I trigger an automated deployment request across CI pipelines?

You trigger an automated deployment request across CI pipelines by simply indicating you are ready to ship or deploy. The workflow then proactively orchestrates the merge, test, version bump, and PR creation sequence.

Do I need Git access to automate PR creation and changelog generation?

Yes, you need Git access to automate PR creation and changelog generation. The release workflow requires integration with your repository's workflows to handle version management, commit pushing, and pull request creation.

When should I not use an end-to-end release automation tool?

You should not use an end-to-end release automation tool if your project lacks standardized version management or requires manual changelog curation. The workflow assumes a predictable VERSION file and Git-based repository workflows.