ship

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines automated release management by orchestrating branch merges, test runs, changelog updates, version bumps, and PR creation in a single, repeatable flow.

Core Features & Use Cases

  • Automates merging main into feature branches and running test suites to validate changes.
  • Generates a clean, bisectable commit history with focused, small commits suitable for release workflows.
  • Produces release notes and PRs, ensuring consistent versioning and changelog updates across teams.

Quick Start

Activate the ship workflow on your feature branch to automatically merge, test, review, bump, 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 release PRs with version bumps and changelog updates?

Automating release PRs involves merging main into feature branches, running tests, updating versions and changelogs, and opening a PR. This workflow ensures predictable, auditable release artifacts with small, bisectable commits.

What is the best way to merge main into feature branches and run tests before a release?

The best way to merge main into feature branches and run tests is through an automated release workflow that validates changes before generating a PR. This ensures consistent versioning and changelog updates across teams.

Can I automate hotfix cycles and feature rollouts for software release pipelines?

Yes, you can automate hotfix cycles and feature rollouts for software release pipelines. The workflow orchestrates branch merges, test runs, and PR creation in a single, repeatable flow to streamline automated release management.

How does a ship workflow produce clean, bisectable commits for release management?

A ship workflow produces clean, bisectable commits by orchestrating branch merges, test runs, and version bumps into focused, small commits suitable for release workflows. It generates release notes and PRs automatically.

Do I need CI or pull-request automation to use an automated release workflow?

You do not need external CI or pull-request automation to use an automated release workflow. The workflow handles merging main, running test suites, updating changelogs, and opening PRs in a single repeatable flow.

Why should I use an automated release workflow instead of manual versioning and PR creation?

Automated release workflows streamline release management by ensuring predictable, auditable release artifacts and consistent versioning. Manual versioning often leads to errors, whereas automation generates release notes and PRs while maintaining a clean commit history.