ship

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

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill ship-bobbo01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill ship-bobbo01

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 pull request. This Skill runs that entire workflow automatically so a feature branch goes from local work to an open PR in one command. ## Core Features & Use Cases - Automated ship pipeline: Detects the base branch and git hosting 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 engineering, design, CEO, and adversarial reviews, runs its own pre-landing review when none exists, and blocks shipping on unresolved issues. - Version 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 on a branch and type "/ship". The Skill merges main, runs the test suite, performs a pre-landing review, bumps the patch version, updates the changelog, commits everything, pushes, and returns the pull request URL. ## Quick Start Ask the assistant to run the ship workflow on your current feature branch to test, version, and open a pull request automatically.

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 creates the PR using the gh or glab CLI, returning the PR URL at the end.

Does the ship workflow support GitLab merge requests?

Yes. The workflow detects the hosting platform from the git remote URL and uses glab for GitLab, including self-hosted instances, falling back to gh for GitHub. If neither CLI is authenticated, it uses git-native commands to detect the default branch.

What happens if tests fail during the ship workflow?

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

Can I ship without running a code review first?

Ship checks a review readiness dashboard for a recent engineering review. If none exists, it runs its own pre-landing review during the workflow. You can also disable the gate globally with gstack-config set skip_eng_review true.

How does the ship workflow choose the version bump?

It automatically selects a MICRO or PATCH bump based on the diff, so you are never prompted for routine releases. It only asks when the changes warrant a MINOR or MAJOR version bump.

When should I not use the automated ship workflow?

Do not run it from the base or default branch, since the workflow aborts there by design. It also stops for unresolvable merge conflicts, plan items marked not done, and review findings that require human judgment.