ship

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tropeks/Vitali --skill ship-tropeks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/tropeks/Vitali/tree/main/.claude/skills/gstack-ship
Command: npx skills add https://github.com/tropeks/Vitali --skill ship-tropeks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship management for code releases is tedious and error-prone. This skill automates the entire ship flow from base branch detection to PR creation, reducing manual steps and human error.

Core Features & Use Cases

  • Detects the target base branch and merges the feature branch into it for a clean PR baseline.
  • Runs tests, reviews diffs, and bumps VERSION while updating CHANGELOG to keep release notes accurate.
  • Commits, pushes, and creates pull requests automatically, with proactive suggestions about deployment when the code is ready. Use cases include releasing a new feature, patch, or hotfix with minimal human intervention and consistent release metadata.

Quick Start

Run the ship workflow on your feature branch to automatically detect the base branch, merge, run tests, update VERSION and CHANGELOG, commit, push, and open 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 branch management and pull request creation?

You can automate git branch management and pull request creation by running a workflow that detects the base branch, merges your feature branch, runs tests, bumps VERSION, and opens a PR automatically. This reduces manual steps and human error.

How does automated CI-CD deployment handle version bumping and changelog updates?

Automated CI-CD deployment handles version bumping and changelog updates by reviewing diffs and automatically updating the VERSION file and CHANGELOG. This ensures release notes remain accurate and consistent across releases without manual intervention.

What is the best way to run tests before opening a pull request?

The best way to run tests before opening a pull request is using an automated ship workflow that merges into the base branch and executes tests as part of the PR baseline. It provides clear visibility into the release process before code is merged.

Does this automated release workflow require specific CI-CD tooling or platforms?

This automated release workflow relies on Git, CI/CD tooling, and PR platforms to coordinate steps like merging, testing, and pull request creation. It integrates with your existing stack to manage deterministic deployment actions.

Can I use this for hotfix and patch releases with minimal human intervention?

Yes, you can use this for hotfix and patch releases with minimal human intervention. It automates merging, test execution, version bumping, and PR creation, providing consistent release metadata for features, patches, and hotfixes.

Why does my automated pull request workflow suggest deployment actions?

An automated pull request workflow suggests deployment actions proactively when code is ready for release. It detects when tests pass and diffs are reviewed, prompting deployment planning to ensure smooth transitions from review to production.