ship

Coordinate the full ship workflow from branch merge to PR creation.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/jayzalowitz/skytwin --skill ship-jayzalowitz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jayzalowitz/skytwin/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/jayzalowitz/skytwin --skill ship-jayzalowitz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seamlessly orchestrates the full software shipping workflow by automating branch prep, tests, diff review, version bump, changelog updates, commit, push, and PR creation.

Core Features & Use Cases

  • Automates base-branch detection and merge; runs test suites; reviews diffs; bumps VERSION; updates CHANGELOG; commits, pushes, and creates a PR.
  • Proactively triggers the workflow when a user indicates readiness to ship or deploy, or when asked to push code or create a PR.
  • Handles guardrails like preflight checks, safety constraints, and artifact generation to ensure reliable shipping.

Quick Start

Prepare your repo and say "ship" to start the automated shipping 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 version bump and changelog updates?

Automated shipping workflows coordinate base-branch detection, test execution, version bumping, changelog updates, commits, pushes, and pull request creation end-to-end. You trigger the workflow by indicating readiness to ship, and it returns the final PR URL for review.

What steps are involved in an end-to-end deploy workflow from tests to PR?

An end-to-end deploy workflow detects and merges the base branch, runs test suites, reviews diffs, bumps the VERSION, updates the CHANGELOG, commits, pushes, and creates a PR. Preflight checks and safety guardrails execute automatically to ensure reliable shipping.

Do I need a specific repository structure to automate branch merging and PR creation?

Automated branch merging and PR creation require a consistent repository structure with established versioning and changelog conventions. Access to versioning files, changelog formatting standards, and PR creation tooling is necessary to coordinate the shipping steps successfully.

What's the best way to streamline CI workflows for versioning and pushing code upstream?

Streamlining CI workflows for versioning involves orchestrating diff reviews, version bumps, and changelog updates in a single automated sequence. Proactively triggering the workflow when expressing readiness to push code upstream coordinates all shipping steps and surfaces the final PR URL.

Why does my automated pull request workflow fail during base branch detection?

Automated pull request workflows fail during base branch detection when repository structures are inconsistent or versioning conventions are missing. The workflow requires consistent repo formatting, access to changelog conventions, and functional PR creation tooling to execute preflight checks and merge operations reliably.

Can I run tests and review diffs before bumping the version in an automated deploy?

Running tests and reviewing diffs before bumping the version is the standard sequence in automated deploy workflows. The system detects and merges the base branch, executes test suites, reviews code diffs, and only then proceeds to bump the VERSION and update the CHANGELOG.