ship

Merge a feature branch, run tests, and prepare a reviewable PR.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bhianerd/aimemory --skill ship-bhianerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/bhianerd/aimemory/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/bhianerd/aimemory --skill ship-bhianerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping changes reliably across branches is hard, because merges, testing, reviews, versioning, changelogs, and PR creation often get handled inconsistently and at different times.

Core Features & Use Cases

  • Fully automated ship workflow: Detects the correct base branch, merges it into your feature branch, runs tests, and prepares a review-ready diff.
  • Quality gates with guardrails: Ensures the required engineering review is cleared (or records an override decision) and surfaces any review items needing your judgment.
  • Release hygiene: Applies an appropriate version bump and updates CHANGELOG, then commits and pushes changes and opens a PR.

Quick Start

  • From your feature branch, ask your assistant to run /ship to automatically merge, test, review, version-bump, update the changelog, commit, push, and create a PR.

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 and running tests from a feature branch?

To automate creating a pull request and running tests, trigger an automated ship workflow that merges the base branch into your feature branch, executes tests, and prepares a review-ready diff.

What is an automated git workflow for release hygiene and versioning?

An automated git workflow for release hygiene applies an appropriate version bump, updates the changelog, and commits changes to ensure consistent versioning and review readiness before opening a pull request.

How do I merge changes with the base branch and handle merge conflicts during continuous integration?

When merging changes with the base branch during continuous integration, the workflow attempts an automated merge and stops explicitly only upon encountering unresolvable conflicts or non-cleared required gates.

Can I push to main and create a PR without manual intervention using an automated workflow?

Yes, you can push to main and create a PR without manual intervention by triggering a non-interactive automation that handles merging, testing, version-bumping, and changelog updates, stopping only for decisions requiring user judgment.

When should I not use an automated shipping workflow for my pull request?

You should not use an automated shipping workflow when your pull request requires user judgment for version-bump decisions, or when you anticipate unresolvable merge conflicts or non-cleared required quality gates demanding manual intervention.