ship

Coordinate release workflows from base branch detection to PR creation.

Updated Apr 12, 2026

Search Tags:#automation #git #release #pr #ci-cd #ship

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)

Core Features & Use Cases

Orchestrates the release process from code readiness to PR creation, ensuring consistent versions and changelogs.
Proactively suggests ship steps when user asks to deploy or push or when context indicates readiness.

Quick Start

Describe what you want shipped and the system will run the full release flow: detect the base branch, run tests, review diffs, bump the version, update 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 my git release workflow from running tests to creating a PR?▼

You can automate the end-to-end git release workflow by triggering a process that detects the base branch, runs tests, reviews diffs, bumps the VERSION file, updates the CHANGELOG, commits, pushes, and creates a PR automatically.

What is the best way to bump version and update changelog before pushing to main?▼

The best way to bump versions and update changelogs before pushing to main is using an automated release workflow that reviews code diffs, increments the VERSION file, updates the CHANGELOG, and then commits and pushes the changes while creating a PR.

How does an automated CI-CD release process handle branch detection and code reviews?▼

An automated CI-CD release process handles branch detection by automatically identifying the base branch, then reviewing code diffs against it before proceeding to bump versions, update changelogs, and create a pull request for final approval.

Can I trigger a pull request creation automatically when my code is ready to ship?▼

Yes, you can trigger pull request creation automatically when code is ready to ship by using a proactive release workflow that engages when you ask to deploy, push code, or create a PR, executing the full shipping sequence.

Do I need external dependencies to automate merging base branches and running tests?▼

No, you do not need external dependencies to automate merging base branches and running tests. The release workflow operates independently using standard tools like Bash, Read, Write, and Edit to execute the shipping sequence.

What are the limitations of proactive release workflow automation for git repositories?▼

Limitations of proactive release workflow automation include its reliance on standard git repository structures for branch detection and its proactive engagement being strictly bound by the user's configured proactive settings to avoid unauthorized pushes.