ship

Orchestrate end-to-end code shipping from merge to PR creation.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill ship-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill ship-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the end-to-end ship workflow, eliminating manual steps from code to PR by orchestrating base-branch detection, merge, tests, diff reviews, version bumps, changelog updates, commits, pushes, and PR creation.

Core Features & Use Cases

  • End-to-end automation of the ship flow: detect the base branch, merge changes, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR.
  • Proactive invocation: can start the ship process when the user signals that code is ready or deployment is desired, without pushing or PR actions happening automatically.
  • Safety and traceability: produces a PR workflow with proper review steps and clear audit trails for each ship event.

Quick Start

Tell Claude to run the ship workflow when your code is ready by issuing /ship.

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 after finishing my code changes?

Automating pull request creation involves detecting the base branch, merging changes, running tests, bumping versions, updating the changelog, and pushing commits to generate a PR URL for review.

What is the best way to automate git versioning and changelog updates before pushing?

Automating git versioning and changelog updates requires an end-to-end ship workflow that reviews diffs, bumps the VERSION file, updates the CHANGELOG, commits, and pushes the changes automatically.

Can I trigger CI/CD ship workflows proactively when my code is ready?

Yes, you can trigger ship workflows proactively by signaling that your code is ready or deployment is desired, which starts the merge, test, and PR creation process without automatically pushing changes beforehand.

Does the ship workflow validate the environment and guard against git merge conflicts?

Yes, the ship workflow validates the environment and guards against merge conflicts by detecting the base branch, ensuring safe automated handoffs, and producing a PR workflow with proper review steps and audit trails.

How do I ensure safe code handoffs when automating pushes to the main branch?

Safe code handoffs when pushing to the main branch are ensured by running tests, reviewing diffs, validating the environment, guarding against conflicts, and producing a PR URL for final review.

What steps are required to ship code changes from a local branch to a deployed PR?

Shipping code changes to a deployed PR requires detecting the base branch, merging, running tests, reviewing diffs, bumping versions, updating the changelog, committing, pushing, and creating the pull request.