ship

Automates merging, testing, versioning, committing, and deploying feature branches via git and GitHub or GitLab CLIs.

107|7|Updated Mar 29, 2026

Search Tags:#git #changelog #versioning #pull request #release automation #deploy #ci cd

One-click install

npx skills add https://github.com/no-session/pstack --skill ship-no-session

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/no-session/pstack/tree/main/ship
Command: npx skills add https://github.com/no-session/pstack --skill ship-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a long checklist 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 release workflow automatically so nothing gets skipped. ## Core Features & Use Cases - Automated ship pipeline: Detects the base branch, merges it into your feature branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a PR or MR. - Review readiness gating: Displays a review dashboard and runs a pre-landing eng review so unreviewed code does not ship silently. - Test framework bootstrap: Detects your runtime (Node, Ruby, Python, Go, Rust, PHP, Elixir) and sets up a test framework if none exists. - Use Case: You finished a feature on a branch and type /ship. The Skill merges main, runs the test suite, auto-generates the changelog entry, bumps the patch version, pushes, and returns the PR URL. ## Quick Start Tell the assistant to ship the current feature branch and it will merge, test, version, commit, push, 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 automate merging, testing, and creating a pull request?▼

Run the /ship command from a feature branch. It fetches and merges the base branch, runs your test suite, reviews the diff, bumps the version, updates the changelog, commits, pushes, and outputs the PR URL without asking for confirmation.

Does this ship workflow work with GitLab as well as GitHub?▼

Yes. The workflow detects the platform from the git remote URL or by checking gh and glab CLI authentication. It uses gh pr commands for GitHub and glab mr commands for GitLab, with git-native fallbacks for unknown platforms.

What happens if my project has no test framework set up?▼

The workflow detects your runtime from files like package.json, Gemfile, or go.mod, researches current best practices, and offers to install and configure a test framework such as vitest, pytest, or minitest. You can decline, which writes a .pstack/no-test-bootstrap marker.

When does the automated ship workflow stop and ask for input?▼

It stops for merge conflicts it cannot auto-resolve, in-branch test failures, review findings needing judgment, MINOR or MAJOR version bumps, missing release pipelines for new binaries, and plan items not marked done. Everything else runs non-interactively.

Can I ship directly from the main or master branch?▼

No. The pre-flight step aborts if you are on the base or default branch and tells you to ship from a feature branch instead. This protects the default branch from unreviewed direct pushes.