ship

Automate the ship workflow from base-branch detection to PR creation.

Updated Apr 18, 2026

Search Tags:#automation #git #release #pr #ship #ci #version-bump

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Shipping software involves a complex sequence of steps from detecting changes on the base branch to merging, testing, bumping versions, updating changelogs, and opening PRs. This Skill automates that end-to-end flow and reduces manual toil.

Core Features & Use Cases

Automated ship workflow: detect base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create PR.
Proactive guidance and safety: ensures actions are taken in the correct order and handles edge cases like conflicts and test failures.
Use Case: When a feature is ready, run /ship to automatically prepare a PR for the main branch with version bump and changelog.

Quick Start

Use the ship skill to automatically run the full release workflow for your current branch, producing a PR URL on success.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate git release workflows from feature branches to pull requests?▼

Automating git release workflows requires running tests, bumping versions, updating changelogs, and creating pull requests in sequence. This end-to-end ship workflow ensures a deterministic release flow on feature branches, reducing manual toil and handling edge cases like conflicts proactively.

What is an end-to-end ship workflow for automated pull request creation?▼

An end-to-end ship workflow automates the sequence from detecting the base branch and reviewing diffs to executing tests, bumping versions, and updating changelogs. It commits and pushes changes, ultimately producing a PR URL to merge the feature branch into the main branch.

Do I need a clean working tree to automate version bumps and changelog updates?▼

Yes, automating version bumps and changelog updates requires a clean working tree and repository access. The workflow performs commits and pushes, so a clean state ensures changes do not conflict with uncommitted local files during the automated release process.

How to handle test failures and conflicts during an automated release flow?▼

Handling test failures and conflicts during an automated release flow is managed by proactive guidance that ensures correct action ordering. The workflow detects edge cases like test failures and conflicts, pausing to provide feedback before completing the PR creation process.

What standard tools are required to automate code shipping and PRs?▼

Automating code shipping and PRs requires standard tools including Git, a test runner, and CI. These tools perform base-branch detection, execute test runs, manage changelog updates, and handle the final commit, push, and pull request creation.

Can I use this automated release flow for any feature branch?▼

Yes, you can use this automated release flow for any feature branch ready for release. The workflow detects the base branch, executes tests, bumps versions, updates the changelog, and prepares a PR URL targeting the main branch upon successful test completion.