ship

Merge base branch, run tests, bump VERSION, update CHANGELOG, and open a pull request.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/24601/gastack-pre-fork --skill ship-24601
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/24601/gastack-pre-fork/tree/main/ship
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill ship-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code requires many manual, error-prone steps: merging the base branch, running tests against the merged state, bumping the version, updating the changelog, committing, pushing, and opening a pull request. Mistakes or missed steps cause broken releases, flaky CI, and wasted review cycles.

Core Features & Use Cases

  • End-to-end ship workflow: Merge the base branch into your feature branch, run test suites, and surface failures or merge conflicts before landing.
  • Release hygiene: Bump semantic VERSION, update CHANGELOG from the diff, commit structured changes, and push a clean, auditable PR.
  • Gating & reviews: Run automated pre-landing reviews, enforce eng-review gates, and stop for human decisions on major version bumps or unresolved conflicts.
  • Use case: From a finished feature branch, run the skill to produce a tested, versioned PR ready for CI and reviewers without manually juggling merges and changelog edits.

Quick Start

Run /ship from your feature branch to merge the base, run tests, bump VERSION, update CHANGELOG, commit, push, and open 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 merging a base branch and running tests before opening a pull request?

Automate merging a base branch and running tests by fetching and merging the base into your feature branch, executing test suites, and surfacing failures or merge conflicts before opening a pull request.

Can I automatically bump semantic versions and update the changelog from git diffs?

Yes, you can automatically bump semantic versions and update the changelog by generating changelog entries directly from git diffs, committing structured changes, and pushing a clean, auditable pull request.

What is the best way to handle merge conflicts when landing a feature branch?

Handling merge conflicts when landing a feature branch involves fetching the base branch, attempting a merge, and stopping the automated shipping process to wait for human decisions when unresolved conflicts are detected.

Does automated versioning stop for human review on major version bumps?

Yes, automated versioning stops for human review on major version bumps by enforcing eng-review gates and pausing the workflow to require human decisions before landing changes.

How do I create a tested and versioned pull request from a feature branch?

Create a tested and versioned pull request by running the shipping workflow from your feature branch to merge the base, run tests, bump VERSION, update CHANGELOG, commit, push, and open a pull request.

What happens if test suites fail during automated branch merging?

If test suites fail during automated branch merging, the workflow surfaces the test failures and stops the process to prevent broken releases and flaky CI from landing in the default branch.