ship

Name: ship
Availability: InStock
Author: singhianand23045

Merge base branch, run tests, and generate PR-ready diffs.

Updated Apr 12, 2026

Search Tags:#automation #changelog #versioning #pr #deploy #ci-cd #ship

Ready to run

npx skills add https://github.com/singhianand23045/GarryTan --skill ship-singhianand23045

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/singhianand23045/GarryTan/tree/main/ship
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill ship-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship pipelines can be error-prone and slow. The Ship skill automates the end-to-end release workflow, reducing manual steps and ensuring consistency across branches and PRs.

Core Features & Use Cases

Automated ship pipeline: detect base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR.
Proactive invocation: trigger ship workflows when the user signals readiness or asks to deploy, without manual pushes.
Safe, auditable releases: maintain predictable release notes and versioning across projects.

Quick Start

Say '/ship' when your code is ready to publish 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 pull request creation and version bumping together?▼

To automate pull request creation and version bumping, the workflow merges the base branch, runs tests, updates the VERSION file and CHANGELOG, commits, pushes, and creates the PR automatically. This ensures consistent releases without manual intervention.

How do I trigger a deploy workflow when my feature branch is ready?▼

You trigger a deploy workflow by signaling readiness, such as using a slash command. The workflow then proactively merges the base branch, runs tests, and prepares the PR diff without requiring manual pushes.

What is the safest way to automate changelog updates and releases across CI workflows?▼

The safest way to automate changelog updates and releases across CI workflows is using an auditable process with guards and fallbacks. This maintains predictable release notes and ensures repeatable deployments across feature branches.

Do I need any external CI-CD dependencies to automate code shipping?▼

No external CI-CD dependencies are required to automate code shipping. The workflow operates independently to merge branches, run tests, bump versions, update changelogs, and create PRs using built-in guards and fallbacks.

Why does my automated release pipeline fail to generate PR-ready diffs?▼

Automated release pipelines fail to generate PR-ready diffs when the base branch is not properly merged or tests fail. The workflow includes fallbacks and auditable release steps to handle these issues safely and maintain predictable versioning.