ship

Automates merging, testing, versioning, and pull request creation for feature branches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves many repetitive manual steps: merging the base branch, running tests, reviewing the diff, bumping versions, updating changelogs, committing, pushing, and opening a pull request. This Skill automates that entire end-to-end release workflow so a feature branch goes from local changes to an open PR with a single command. ## Core Features & Use Cases - Fully Automated Ship Pipeline: Detects the base branch, merges it, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the PR without interactive prompts. - Review Readiness Gate: Displays a review dashboard (Eng, CEO, Design, Adversarial reviews) and gates shipping on engineering review status, with staleness detection against the current HEAD commit. - Test Framework Bootstrap: Detects the project runtime (Node, Ruby, Python, Go, Rust, PHP, Elixir) and sets up a test framework with best-practice research when none exists. - Use Case: After finishing a feature branch, a developer says "ship it" and the Skill merges main, runs the test suite, auto-generates the changelog entry, creates bisectable commits, and returns the PR URL. ## Quick Start Ask the assistant to ship the current feature branch by running the ship workflow and creating a pull request.

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 from a feature branch?

Run the ship workflow, which detects the base branch, merges it into your feature branch, runs tests, bumps the version, updates the changelog, commits, pushes, and creates the PR using the GitHub CLI. It outputs the PR URL when finished.

How does the ship workflow handle merge conflicts with the base branch?

Simple conflicts in files like VERSION or CHANGELOG are auto-resolved. Complex or ambiguous conflicts stop the workflow and display the conflicting files so you can resolve them manually before re-running.

Can the ship workflow run without an existing test framework?

Yes. It detects your project runtime (Node, Ruby, Python, Go, Rust, PHP, or Elixir), researches current testing best practices, and offers to install and configure a framework such as vitest, pytest, or minitest with an example test.

Does the ship workflow require a code review before creating a PR?

By default it gates on an engineering review from the past 7 days, shown in a review readiness dashboard. You can override the gate per branch, or disable it globally with the skip_eng_review config setting.

What happens if tests fail during the ship workflow?

In-branch test failures stop the workflow so they can be fixed. Pre-existing failures unrelated to your changes are triaged and reported rather than automatically blocking the ship.