ship

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill ship-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack/ship
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill ship-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a repetitive chain of manual steps: merging the base branch, running tests, reviewing the diff, bumping the version, updating the changelog, committing, pushing, and opening a PR. This Skill runs that entire workflow end-to-end so a feature branch goes from local work to an open pull request with one command. ## Core Features & Use Cases - Automated ship pipeline: Detects the base branch and platform (GitHub via gh or GitLab via glab), merges the base branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the PR/MR. - Review readiness gating: Displays a review dashboard from prior eng/CEO/design/adversarial reviews, runs its own pre-landing review when none exists, and blocks shipping on unresolved issues. - Versioning and changelog automation: Auto-selects MICRO or PATCH version bumps, generates changelog entries from the diff, and splits large changesets into bisectable commits. - Use Case: You finished a feature branch and say "ship it". The Skill merges main, runs the test suite, fixes auto-fixable review findings, bumps the version, and returns the PR URL without further prompts. ## Quick Start Ask the assistant to ship the current feature branch by running the /ship workflow and returning the pull request URL.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a pull request automatically from a feature branch?

Run the /ship workflow from your feature branch. It merges the base branch, runs tests, reviews the diff, bumps the version, updates the changelog, commits, pushes, and opens the PR, returning the URL at the end.

Does the ship workflow support GitLab as well as GitHub?

Yes. The workflow detects the platform from the git remote URL, using gh for GitHub and glab for GitLab, including self-hosted instances. If neither CLI is available, it falls back to git-native commands for base branch detection.

What happens if tests fail during the ship workflow?

In-branch test failures stop the workflow so you can fix them. Pre-existing failures from the base branch are triaged rather than auto-blocking, so unrelated breakage does not prevent shipping your changes.

Can I ship without running an engineering review first?

Yes. If no prior eng review exists, ship runs its own pre-landing review during the workflow. You can also disable the eng review gate globally with gstack-config set skip_eng_review true.

How does the ship workflow handle version bumps and changelogs?

It auto-selects MICRO or PATCH bumps without asking, and only prompts for MINOR or MAJOR bumps. Changelog entries are generated automatically from the diff, and large changesets are split into bisectable commits.

When does the ship workflow stop and ask for input?

It stops for merge conflicts it cannot resolve, test failures, review findings needing judgment, MINOR or MAJOR version bumps, low test coverage, incomplete plan items, and missing release pipelines for new binaries.