ship

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

1|Updated Mar 28, 2026

Search Tags:#automation #workflow #versioning #ship #CHANGELOG #ci #pull-request

Ready to run

npx skills add https://github.com/shhubbh/flowstate --skill ship-shhubbh

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflows require manual, error-prone steps to move code from feature branches to production. This Skill automates detect + merge base branch, run tests, review diff, bump version, update CHANGELOG, commit, push, and create a PR, reducing human toil and bottlenecks.

Core Features & Use Cases

Detects the base branch, merges it for local testing, and runs the full test suite automatically.
Bumps VERSION, updates CHANGELOG, commits changes, and opens a PR to merge to main.
Proactively suggests deployment readiness when asked or when code is ready for production.

Quick Start

Initiate a ship command to automatically package, test, and publish your changes with 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 a Git workflow to merge base branches and create pull requests?▼

Automating a Git workflow to merge base branches and create pull requests requires a remote repository with base branch tracking. The process merges the base branch locally, runs tests, bumps versions, updates the CHANGELOG, and opens a PR via GitHub or GitLab APIs.

How does automated version bumping and CHANGELOG updates work for continuous integration?▼

Automated version bumping and CHANGELOG updates work by modifying VERSION files and changelog entries during the release flow. The automation commits these changes locally before pushing, ensuring versioning metadata stays synchronized with daily commits and hotfixes.

Do I need GitHub or GitLab API access to automate end-to-end code shipping?▼

Yes, you need GitHub or GitLab API access to automate end-to-end code shipping. The workflow requires tooling to create PRs via these APIs, along with a Git workflow that supports base branch tracking and a remote repository to push commits.

What's the best way to run tests automatically before merging feature branches to main?▼

The best way to run tests automatically before merging feature branches to main is to detect and merge the base branch locally first. This ensures local testing against the latest state before bumping versions and opening a pull request.

Can I use automated release flows for hotfixes across multiple Git branches?▼

Yes, you can use automated release flows for hotfixes across multiple Git branches. The automation applies to teams who want a hands-off release flow for daily commits, hotfixes, or feature deployments, managing merges and PRs end-to-end.

When should I not use an automated pull request creation workflow?▼

You should not use an automated pull request creation workflow if your repository lacks a Git workflow with base branch tracking or remote repository access. The automation requires tooling to modify VERSION and CHANGELOG files and create PRs via GitHub or GitLab APIs.