ship

Automate end-to-end code shipping from base-branch merge to PR creation.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Andy-HNU/AndyClaw --skill ship-andy-hnu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-ship
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill ship-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end shipping workflow for software changes: detecting the base branch, merging for test visibility, running tests, reviewing diffs, bumping the version, updating the changelog, committing, pushing, and creating a PR.

Core Features & Use Cases

  • Auto-detects the base branch and merges into the feature branch for accurate test results.
  • Runs the full test suite and halts on failures to ensure a safe, shippable state.
  • Bumps the version number and updates CHANGELOG automatically, then commits and pushes.
  • Creates a pull request, optionally with proactive suggestions when code is ready or deployment is asked.
  • Suitable for workflows where you want a hands-off ship process that reduces drift between branches.

Quick Start

Tell me to ship and I will execute the full end-to-end 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 creating a pull request and running tests before merging code?

You can automate the end-to-end shipping workflow by using a single command that merges the base branch, runs tests, bumps versions, and creates a pull request automatically.

What is the best way to ensure my feature branch has accurate test results before pushing?

The best way to ensure accurate test results is to auto-detect and merge the base branch into your feature branch first, then run the full test suite to catch integration issues.

Can I automatically bump the version number and update the changelog when pushing code?

Yes, you can automatically bump the version number and update the changelog as part of a hands-off shipping process that commits and pushes the changes before creating a pull request.

Does the automated shipping flow halt if my test suite fails?

Yes, the automated shipping flow runs the full test suite and halts immediately on failures to ensure your code remains in a safe, shippable state before creating a pull request.

How do I reduce branch drift when preparing code for deployment?

To reduce branch drift, you can use an automated workflow that merges the base branch into your feature branch and commits the updated code before pushing it for pull request review.