ship

Automates Git release workflows from base-branch merge to PR creation and deployment using gstack tooling.

Updated Apr 1, 2026

Search Tags:#automation #git #changelog #ship #pull-request #version-bump #release-workflow

Ready to run

npx skills add https://github.com/whd4/gstack --skill ship-whd4

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation orchestrates the end-to-end release workflow from base-branch merge to PR creation and deployment, reducing manual toil and human error.

Core Features & Use Cases

Automates merging into the base branch, running tests, reviewing diffs, bumping versions, updating the changelog, committing, pushing, and creating a PR.
Proactively invokes the release flow when the user indicates code is ready or deployment is requested, coordinating with CI/CD and version control.
Suitable for teams seeking a repeatable, auditable ship process across repositories.

Quick Start

Tell me to ship your latest changes and I will orchestrate the release steps end-to-end.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate my git release workflow from running tests to creating a pull request?▼

Automating a git release workflow involves detecting the base branch, running tests, generating diffs, updating changelogs, bumping versions, and pushing commits to open a pull request. This orchestrates the end-to-end ship process to reduce manual toil and human error.

What is the best way to coordinate version bumps and changelog updates before deploying code?▼

Coordinating version bumps and changelog updates requires a release workflow that automatically generates diffs, increments versions, and commits changes before pushing. This ensures repeatable, auditable deployment processes across Git repositories by orchestrating these steps sequentially.

Can I use an automated pull request workflow across multiple Git repositories?▼

Yes, an automated pull request workflow can coordinate shipping code across repositories by detecting the base branch, running tests, and opening PRs. It applies to teams needing a repeatable, auditable release process across multiple Git repos.

How do I trigger an end-to-end deployment process when my code is ready?▼

Triggering an end-to-end deployment process happens when you indicate your code is ready or request deployment. The workflow proactively invokes the release flow, coordinating with CI/CD and version control to merge, test, bump versions, and open PRs.

Do I need gstack tooling to automate my pull request and version bump workflow?▼

Yes, automating the pull request and version bump workflow uses gstack tooling to detect base branches, run tests, update changelogs, and open PRs. It orchestrates these release steps within Git repositories to ensure an auditable ship process.