ship

Merge base branch, run tests, bump version, and create a pull request.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MANUAL TRIGGER ONLY: invoke only when user types /ship. Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying.

Core Features & Use Cases

  • Manual trigger via /ship to start a defined ship workflow.
  • Automates branch merge, test execution, changelog and version bumps, commits, and PR creation.
  • Proactively surface deployment readiness suggestions and support multi-destination routing.

Quick Start

Type /ship to start the 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 creating a pull request with a version bump and changelog update?

Automating a pull request with a version bump and changelog update is handled by the ship workflow, which merges the base branch, runs tests, updates the version, and creates a PR triggered by the /ship command.

What does an automated ship workflow do before merging code to the main branch?

An automated ship workflow merges the base branch into your current branch and runs tests to ensure consistent changes before promoting code via a pull request.

How do I trigger an automated deploy and push to main workflow?

Triggering an automated deploy and push to main workflow requires typing the /ship command, which initiates the branch merge, test, version bump, and PR creation sequence.

Does this ship workflow automation work with codebases that have formal release governance?

This ship workflow automation is designed for codebases with formal release governance to ensure consistent changes and reviews are enforced before promotion.

Can I proactively suggest deployment readiness when my code is ready?

Proactively suggesting deployment readiness is supported when you indicate your code is ready or ask about deploying, surfacing the automated ship workflow.

What is the best way to ensure consistent reviews before promoting code changes?

Ensuring consistent reviews before promoting code changes is achieved by automating deterministic steps, version bumps, and changelog updates into a formal pull request creation process.