ship

Merge base into feature branch, run tests, update versioning, and create a pull request.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/steffenpharai/StartupFramework --skill ship-steffenpharai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/steffenpharai/StartupFramework/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/steffenpharai/StartupFramework --skill ship-steffenpharai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship your code from a feature branch into a merge-ready PR with automated testing, reviews, and versioning, reducing manual toil and error-prone handoffs.

Core Features & Use Cases

  • Pre-flight base-branch detection and merge to ensure tests run in the merged state.
  • Run full test suites, perform quick validations, and enforce gating via reviews.
  • Bump VERSION, update CHANGELOG, commit, push, and create a PR against the base branch.
  • Proactively suggest next steps when code is ready for deployment or release.

Quick Start

Run the ship workflow on your feature branch to automatically create a PR against the base branch.

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 tests and changelog updates?

To automate creating a pull request, the workflow merges the base branch into your feature branch, runs tests, bumps versions, updates the changelog, and opens a PR. This automated shipping process reduces manual toil and ensures your code is merge-ready.

How do I run tests in a merged state before opening a pull request?

Running tests in a merged state is handled by pre-flight base-branch detection. The workflow automatically merges the base into your feature branch, installs dependencies, and executes your full test suite to validate the code before creating a PR.

Can I automate pre-merge ship workflows for monorepos and multi-language projects?

Yes, you can automate pre-merge ship workflows for monorepos and multi-language projects. The process is optimized to handle complex environments by fetching origin, merging the base, running tests, and creating a PR across multiple languages.

What happens when there are merge conflicts or pending reviews during PR automation?

When merge conflicts or pending reviews occur during PR automation, the workflow enforces gating. It proactively halts the automated shipping process and suggests next steps, ensuring that code is not merged until conflicts are resolved and reviews are passed.

Do I need Git and gh to automate shipping code to pull requests?

Yes, you need Git and gh to automate shipping code. The workflow relies on Git, gh, bun, and Node environments to fetch the origin branch, merge the base, install dependencies, run tests, and create a pull request.

What is the best way to ship code from a feature branch into a merge-ready PR?

The best way to ship code into a merge-ready PR is to run an end-to-end shipping workflow. It automatically merges the base, validates with tests, updates versioning and changelogs, and creates a PR, reducing manual errors and handoffs.