ship

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a feature branch involves many repetitive, error-prone steps: merging main, running tests, reviewing the diff, bumping versions, updating the changelog, splitting commits, and opening a PR. This Skill automates the entire release workflow end-to-end so a single command takes a branch from development to an open 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 review checklist to the diff, surfacing critical and informational issues before code lands. - Versioning & Changelog: Auto-decides MICRO/PATCH version bumps in 4-digit format and generates CHANGELOG entries from commits and diffs. - Bisectable Commits & PR Creation: Splits changes into logical commits, pushes the branch, and opens a GitHub PR via gh with a full summary. - Use Case: A developer finishes a feature branch and types /ship; the workflow tests, reviews, versions, commits, pushes, and returns a PR URL without further interaction. ## Quick Start Run the /ship command from your feature branch to test, review, 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 GitHub pull request from a feature branch?▼

Run the /ship workflow from your feature branch. It merges origin/main, runs tests, bumps the version, updates the changelog, commits in logical chunks, pushes, and creates the PR using the gh CLI, returning the PR URL.

How to run tests before merging a feature branch into main?▼

The workflow merges origin/main into your branch first, then runs the Rails test suite and Vitest in parallel. If any test fails, the process stops and shows the failures before any commit or push occurs.

Does the ship workflow work on the main branch?▼

No, the workflow aborts immediately if you are on the main branch. It is designed to ship feature branches only, so you must check out a feature branch before running it.

How is the version bump level decided automatically?▼

The workflow counts changed lines in the diff: under 50 lines triggers a MICRO bump, 50 or more triggers PATCH. MINOR and MAJOR bumps require explicit user confirmation since they signal major features or breaking changes.

What happens when the pre-landing review finds critical issues?▼

Each critical issue is presented with a recommended fix and three options: fix it now, acknowledge and ship anyway, or mark as false positive. If you choose to fix, the fixes are committed and you must rerun /ship to retest.

When are LLM eval suites run during the ship workflow?▼

Eval suites run only when the diff touches prompt-related files such as prompt builders, generation services, evaluators, or system prompt files. Affected suites are identified via PROMPT_SOURCE_FILES declarations and run at the full judge tier.