ship

Automates the git ship workflow from branch merge through tests, version bump, and PR creation.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill ship-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill ship-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping code involves a repetitive checklist: 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 sequence as one automated workflow so nothing gets skipped. ## Core Features & Use Cases - End-to-end ship pipeline: Detects the base branch and git platform (GitHub/GitLab), merges the base branch, runs test suites, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates or updates the PR. - Quality gates: Runs a pre-landing review, test failure ownership triage (in-branch vs pre-existing), coverage checks, and a review readiness dashboard before allowing the ship to proceed. - Test framework bootstrap: Detects projects with no test setup and scaffolds a framework, example tests, CI workflow, and TESTING.md. - Use Case: You finish a feature 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 Ask the assistant to ship the current feature branch by running the ship workflow and opening a pull request.

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 PR after finishing 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 or updates the pull request automatically.

What does the ship workflow do when tests fail?

It classifies each failure as in-branch or pre-existing. In-branch failures stop the ship. Pre-existing failures are triaged based on repo mode: solo repos offer to fix them, collaborative repos offer to file an issue assigned to the likely author.

Does the ship skill work with GitLab as well as GitHub?

Yes. It detects the platform from the git remote URL and uses gh for GitHub or glab for GitLab, with git-native fallbacks when neither CLI is authenticated. PR or MR creation adapts to the detected platform.

Can I re-run the ship workflow after it already ran once?

Yes, it is idempotent. Verification steps like tests and reviews always re-run, but actions are skipped if already done: an existing version bump is reused, an existing push is skipped, and an existing PR body is updated instead of recreated.

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

The ship workflow detects the missing framework and offers to bootstrap one. It researches best practices for your runtime, installs packages, writes example tests, adds a CI workflow, and documents conventions in TESTING.md.