ship

Automate feature branch merges, tests, version bumps, changelog updates, and PR creation.

Updated Apr 20, 2026

Search Tags:#automation #git #workflow #testing #ship #ci #pull-request

Ready to run

npx skills add https://github.com/GS-Personal/gstack --skill ship-gs-personal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/GS-Personal/gstack/tree/main/ship
Command: npx skills add https://github.com/GS-Personal/gstack --skill ship-gs-personal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow automates the end-to-end process of delivering code: merging main, running tests, reviewing diffs, bumping versions, updating CHANGELOG, committing, pushing, and creating PRs.

Core Features & Use Cases

Fully automated PR ship: merges feature branches into main, runs tests, updates version numbers, and opens a PR for review.
Safe auto-resolutions and guardrails: detects and aborts on complex merge conflicts or failing tests, ensuring stability.
Versioning and traceability: auto-bumps version, updates changelog, and provides a clear history for audits.

Quick Start

Trigger the ship workflow on a feature branch to automatically merge, test, version, and open the PR.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate a Git pull request workflow from merge to PR creation?▼

To automate a Git pull request workflow, you can trigger a predefined process that merges origin/main into a feature branch, runs tests, updates the VERSION and CHANGELOG, commits, pushes, and opens a PR. This handles the end-to-end ship workflow deterministically.

What happens to automated version bumps and changelog updates when tests fail?▼

When tests fail during the automated ship workflow, the process aborts before performing version bumps or changelog updates. This guardrail ensures that only passing, stable code branches proceed to versioning and PR creation.

How do I resolve merge conflicts when automating a feature branch ship workflow?▼

When automating a feature branch ship workflow, the process detects complex merge conflicts during the origin/main merge and safely aborts. This prevents bad merges, requiring manual conflict resolution before re-triggering the automated workflow.

Can I use automated PR creation and testing in a standard Git CI environment?▼

Yes, you can use automated PR creation and testing in Git-based CI environments. The workflow applies to feature branches prepared for integration, executing deterministic merges, test runs, and PR provisioning without requiring additional dependencies.

What is the best way to prepare a feature branch for integration with automated versioning?▼

The best way to prepare a feature branch for integration is to run an end-to-end ship workflow that automatically merges main, runs tests, bumps versions, updates the changelog, and opens a PR for review.

Why does my automated Git workflow abort before opening a pull request?▼

Your automated Git workflow aborts before opening a pull request if it encounters complex merge conflicts or failing tests during the process. This safety mechanism ensures only stable, conflict-free code is provisioned for review.