skills.rest
VertaKhan
VertaKhanCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate release workflows from feature branch to pull request.

Updated Apr 5, 2026
Search Tags:#automation#git#workflow#release#pr#ship
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill ship-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill ship-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship skill provides a fully automated release workflow that detects the base branch, merges, runs tests, bumps the VERSION, updates the CHANGELOG, commits, pushes, and opens a pull request so you can ship reliably.

Core Features & Use Cases

  • End-to-end release automation from a feature branch to main.
  • Deterministic merges with conflict handling and pre-landing checks.
  • Version bumping and changelog updates aligned with your project rules.
  • Automated PR creation and lightweight telemetry for usage insights.

Quick Start

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

Automated git release workflows handle merging your feature branch, running tests, bumping the VERSION, updating the CHANGELOG, and opening a pull request. This ensures a hands-off, auditable release flow from feature to default branch.

Can I automatically update the changelog and version file during a branch merge?▼

Yes, automated release scripts can bump the VERSION file and update the CHANGELOG simultaneously when merging a branch. This aligns version bumps and changelog updates with your project rules before pushing the commit.

What does an automated PR workflow do if there are merge conflicts?▼

Automated PR workflows include safety checks for conflicts and pre-landing reviews to ensure deterministic merges. If conflicts are detected during the base branch merge, the process stops to prevent bad releases.

Do I need to configure test commands before automating a pull request release?▼

Yes, you must provide test commands, git access, and a versioning strategy to automate a pull request release. The workflow runs these tests after merging the feature branch but before bumping the version and opening the PR.

What is the best way to ensure deterministic releases when merging feature branches?▼

The best way to ensure deterministic releases is using an automated workflow with conflict handling and pre-landing checks. This guarantees tests pass, versions bump correctly, and changelogs update before pushing to the default branch.

Why does my automated branch merge fail before creating a pull request?▼

Automated branch merges fail before creating a pull request if safety checks detect conflicts or if configured test commands fail. These pre-landing reviews prevent incomplete or conflicting code from landing in the default branch.

Related Skills

Explore More Software Engineering Skills→
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced
ibalasiteibalasite

ship

Merge a feature branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

Community
Advanced
abustamamabustamam

ship

Automate release workflows by merging branches, running tests, and opening PRs.

Community
Advanced
ilonatommyilonatommy
3

commit-squashing

Consolidate multiple Git commits into a single commit using rebase, reset, or merge strategies.

Community
Intermediate