ship

Automate pre-merge shipping by merging, testing, and creating a PR.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill ship-zaeem-rafiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/zaeem-rafiq/tatheer-swift-sdk/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill ship-zaeem-rafiq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the entire pre-merge shipping process so teams can reliably push code with confidence, reducing manual steps and human error.

Core Features & Use Cases

  • Detect base branch and merge into the feature branch
  • Run tests, evaluate results, and update versioning and changelog
  • Commit, push changes, and create a PR automatically
  • Handle conflicts and gating decisions in a deterministic way

Quick Start

Issue /ship to trigger the automated shipping flow that merges, tests, and opens 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 pre-merge git workflows to create pull requests?

Automated pre-merge shipping merges the base branch into your feature branch, runs tests, bumps the VERSION, updates the CHANGELOG, and creates a PR. This end-to-end workflow uses git commands and PR tooling to reduce manual steps and human error.

What is a fully automated shipping workflow for continuous integration?

A fully automated shipping workflow detects the base branch, merges it into the feature branch, runs tests, and updates versioning and changelogs. It operates in non-interactive mode to handle conflicts and gating decisions deterministically.

How do I automatically update version and changelog files before opening a PR?

Automated shipping pipelines review diffs after merging the base branch, then bump the VERSION and update the CHANGELOG automatically. This ensures versioning and changelog updates are reproducible across environments before pushing and creating a PR.

Does automated pre-merge shipping handle git merge conflicts and test failures?

Automated pre-merge shipping handles git merge conflicts and test failures as part of a seamless pipeline. It processes these gating decisions in a deterministic way to ensure reproducible results without manual intervention.

Can I run an end-to-end git merge and PR creation process in non-interactive mode?

Automated shipping workflows operate entirely in non-interactive mode to execute end-to-end git merges, tests, commits, and pushes. This triggers a fully automated pipeline that creates a pull request upon successful completion.

What's the best way to detect the base branch and merge into a feature branch automatically?

Automated shipping workflows detect the base branch and merge it into the feature branch automatically. This approach relies on git commands to ensure reproducible results across environments before running tests and creating a PR.