ship

Automate the ship workflow for software changes with tests, changelog updates, and PR creation.

12|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/shogo-labs/shogo-ai --skill ship-shogo-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/virtual-engineering-team/.shogo/skills/gstack-ship
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill ship-shogo-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly and reliably ships software changes by automating the end-to-end release workflow, including base-branch detection, tests, changelog updates, version bumps, and PR creation.

Core Features & Use Cases

  • Automates the ship process across feature and release branches, coordinating git commands, test execution, changelog generation, versioning, and PR creation.
  • Ensures consistent release hygiene by updating the version, writing changelogs, and pushing a PR for review.
  • Use case: when preparing a release, trigger the ship workflow to gate changes and open a PR automatically.

Quick Start

Initiate the ship workflow by asking to ship your current branch to main or by saying the trigger phrase for the Ship skill.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git release workflows with changelog updates and PR creation?

Automating git release workflows involves detecting the base branch, running tests, bumping versions, updating changelogs, and pushing a PR. This ship workflow coordinates git operations and test execution to ensure consistent release hygiene across feature and release branches.

What is the best way to coordinate version bumps and changelog generation before opening a pull request?

Coordinating version bumps and changelog generation requires an automated ship workflow that updates versioning, writes changelog entries, and submits a PR. This ensures release hygiene by gating changes through automated tests before pushing to the remote repository for review.

Do I need a main branch and configured test commands to automate PR creation?

Yes, automating PR creation requires a repository with a main branch, configured test commands, and remote access to push changes. The ship workflow detects the base branch and runs tests before opening a pull request for review.

Can I use this ship workflow on both feature branches and release branches?

Yes, the ship workflow applies to typical release scenarios on both feature and release branches. It coordinates git commands, test execution, changelog generation, versioning, and PR creation across teams to reliably ship software changes.

How does base-branch detection work when preparing a release from a feature branch?

Base-branch detection identifies the target branch for merging your software changes during the release workflow. The ship process uses this detection to coordinate test execution, changelog updates, version bumps, and PR submission from your current feature or release branch.

When should I not use an automated ship workflow for git operations?

You should avoid automated ship workflows if your repository lacks a main branch, configured test commands, or remote push access. The automation depends on these prerequisites to detect the base branch, run tests, bump versions, and open pull requests reliably.