ship

Merge base branch, run tests, bump VERSION, and create a PR.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/zzxtbeta/design-handbook --skill ship-zzxtbeta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/ship
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill ship-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow, turning a set of code changes into a ready-to-ship PR with minimal manual steps.

Core Features & Use Cases

  • End-to-end ship workflow: detect and merge base branch, run tests, review diff, bump version, update CHANGELOG, commit, push, and create PR.
  • Proactive deployment guidance: suggests next steps when code is ready to ship, and helps coordinate pre-release checks.
  • Deterministic task execution: uses the listed tools to guarantee repeatable release steps.

Quick Start

Trigger the ship skill to run the full release workflow from base-branch merge to PR creation.

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

To automate your git release workflow, you can trigger a process that merges the base branch, runs tests, bumps the VERSION, updates the CHANGELOG, and pushes changes to create a ready-to-review PR.

What is the best way to prepare a feature branch for a code release?

Preparing a feature branch for a code release involves detecting the base branch, merging it into your feature branch, running tests, and reviewing the diff to ensure release readiness.

Can I automatically bump the version and update the changelog before creating a pull request?

Yes, you can automatically bump the VERSION and update the CHANGELOG before committing and pushing changes, which ensures the pull request includes all necessary release metadata.

Does the automated ship workflow require manual steps to coordinate release checks?

No, the automated ship workflow coordinates release checks deterministically using built-in tools, requiring minimal manual steps to turn code changes into a ready-to-ship PR.

How do I ensure a repeatable and deterministic PR creation process for version updates?

You can ensure a repeatable PR creation process by using an automated workflow that sequences base-branch merges, test runs, version bumps, and changelog updates to produce consistent release PRs.

What should I do when my automated release workflow fails to detect the base branch?

When the automated release workflow fails to detect the base branch, verify your git configuration and branch context to ensure the tool can correctly identify and merge the target base branch.