ship

Merge base branch, run tests, bump version, update changelog, and create a pull request.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/rkumar261/studio-cast --skill ship-rkumar261
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/rkumar261/studio-cast --skill ship-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship workflow automates the end-to-end release process by merging the base branch into the feature branch, running tests, bumping the version, updating the changelog, committing, pushing, and creating a pull request.

Core Features & Use Cases

  • Automatically detect the base branch and merge into the feature branch for consistent test runs.
  • Run test suites and verify results before shipping, ensuring regressions are caught early.
  • Bump the VERSION, update CHANGELOG, commit changes, push, and open a PR to enable safe, auditable releases.
  • Proactively assist with deployment decisions and generate a clean PR payload for code review.

Quick Start

Run the ship workflow on your feature branch to automatically merge base, run tests, update version, 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 a git release workflow from feature branch to pull request?

To automate a git release workflow from a feature branch to a pull request, you need a process that merges the base branch, runs tests, bumps the version, updates the changelog, and opens a PR. This ensures safe, auditable releases with safety checks baked in.

Can I automatically bump the version and update the changelog before creating a PR?

Yes, you can automatically bump the version and update the changelog before creating a PR. Automating these steps as part of your release workflow ensures your version control is consistent and your changelog is always current when opening a pull request.

What is the best way to run tests before merging a feature branch into the main branch?

The best way to run tests before merging into the main branch is to automate the process by first merging the base branch into your feature branch. This ensures consistent test runs and catches regressions early before opening a pull request.

Do I need GitHub CLI to automate pull request creation from a feature branch?

Yes, you need GitHub CLI to automate pull request creation from a feature branch. Coordinating the end-to-end release workflow, including merging, testing, version bumping, and opening a PR, requires both git and GitHub CLI.

Why should I merge the base branch into my feature branch before running tests?

You should merge the base branch into your feature branch before running tests to ensure consistent test runs. This approach catches regressions early by testing your feature code against the latest state of the main branch before opening a PR.