ship

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill ship-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill ship-vertakhan

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 release workflow end-to-end from a single command. ## Core Features & Use Cases - Automated Ship Pipeline: Detects the git hosting platform (GitHub or GitLab), merges the base branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the PR or MR. - Review Readiness Gate: Displays a review readiness dashboard and runs a pre-landing engineering review so unreviewed code does not ship silently. - Smart Versioning and Changelog: Auto-selects MICRO or PATCH version bumps and generates changelog content from the diff, asking only when a MINOR or MAJOR bump is needed. - Use Case: You finished a feature branch and type /ship. The workflow merges main, runs the test suite, splits the changeset into bisectable commits, bumps the version, and returns the pull request URL without further prompts. ## Quick Start Ask the AI 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 automate creating a pull request 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 gh or glab, returning the PR URL at the end.

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

Yes, the workflow detects the hosting platform from the git remote URL and uses gh for GitHub or 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 there are merge conflicts during shipping?▼

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 I ship code without running an engineering review?▼

Ship runs its own pre-landing review if no recent engineering review exists. You can disable the gate globally with gstack-config set skip_eng_review true, after which the dashboard shows the review as skipped and shipping proceeds.

How does the workflow decide the version bump type?▼

MICRO and PATCH bumps are selected automatically based on the changeset. The workflow only pauses to ask when the diff indicates a MINOR or MAJOR bump is appropriate, since those carry larger release implications.

Why does ship abort when I run it on the main branch?▼

Shipping from the base branch is blocked by design because the workflow exists to land feature branch work. Switch to a feature branch containing your changes and run the command again.