ship

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill ship-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill ship-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a feature branch involves many repetitive, error-prone steps: merging main, running test suites, reviewing the diff, bumping the version, writing the changelog, splitting commits, pushing, and opening a PR. This Skill automates the entire workflow end-to-end so a single command takes a branch from local work to a ready pull request. ## Core Features & Use Cases - Automated pre-merge pipeline: Merges origin/main, runs Rails and Vitest suites in parallel, and conditionally runs LLM eval suites when prompt-related files change. - Pre-landing review: Applies a structured checklist to the diff, surfacing critical and informational issues before merge. - Versioning and changelog: Auto-decides MICRO/PATCH bumps in a 4-digit VERSION format and generates a categorized CHANGELOG entry from the full branch diff. - Bisectable commits and PR creation: Splits changes into logical commits, pushes the branch, and creates a GitHub PR via gh with test results and review findings. - Use Case: A developer finishes a feature branch and types /ship; the workflow tests the merged code, reviews the diff, bumps the version, and returns the PR URL without further interaction. ## Quick Start Run the /ship command from a feature branch to test, review, 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 creating a pull request from a feature branch?▼

Run the /ship workflow from your feature branch. It merges origin/main, runs the test suites, reviews the diff, bumps the version, updates the changelog, commits in logical chunks, pushes, and creates the PR with gh pr create, returning the PR URL.

How does the ship workflow decide the version bump level?▼

It auto-decides based on diff size: under 50 changed lines triggers a MICRO bump, 50 or more lines triggers PATCH. MINOR and MAJOR bumps are only applied after asking the user, and bumping a digit resets all digits to its right to zero.

What happens when tests fail during the ship workflow?▼

The workflow stops immediately and shows the failures. Tests run on the merged state of the branch and origin/main, and the process never proceeds past a failing Rails or Vitest suite.

When are LLM eval suites run before merging?▼

Evals run only when the diff touches prompt-related files such as prompt builders, generation services, evaluators, or system prompt files. Affected suites are matched via PROMPT_SOURCE_FILES declarations and run at the full judge tier as a pre-merge gate.

Can I run the ship workflow from the main branch?▼

No. The workflow aborts immediately if you are on main and instructs you to ship from a feature branch. It also stops on unresolvable merge conflicts or critical review findings the user chooses to fix.

Why does the ship workflow split changes into multiple commits?▼

Splitting creates bisectable commits where each commit represents one logical change, ordered so dependencies come first. This makes git bisect effective and keeps every intermediate commit independently valid.