ship

Automate release workflows from base-branch detection to pull request creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow from detecting the base branch to creating a pull request, eliminating manual handoffs and accelerating shipping.

Core Features & Use Cases

  • End-to-end release automation: detect base branch, run tests, merge when green, bump VERSION, update CHANGELOG, commit, push, and create a PR.
  • Proactive release readiness: ensures changes are ready to ship by validating tests and diffs before merging.
  • Safe deployment policy: bypass direct pushes and always push via PRs to preserve review and traceability.

Quick Start

Start the ship workflow by requesting a release; it will perform all steps automatically and return the PR URL when created.

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 testing to pull request creation?

You can automate a git release workflow by running tests, validating diffs, updating the changelog, and creating a pull request. This ensures release readiness by validating checks and deferring direct pushes in favor of PR-based changes.

What is the safest way to automate version bumps and changelog updates for routine releases?

The safest way to automate version bumps and changelog updates is to detect the base branch, validate tests, and push changes via a pull request rather than direct commits. This preserves review traceability and ensures changes are ready to ship.

Can I use automated release automation for both routine releases and hotfixes across Git repositories?

Yes, automated release automation applies to both routine releases and hotfixes across Git repositories. It coordinates test runs, merge checks, version bumps, changelog updates, commits, and PR creation end-to-end.

Does this release automation tool bypass direct pushes to the base branch?

No, this release automation tool enforces a safe deployment policy that bypasses direct pushes. It always pushes code changes via pull requests to preserve review processes and maintain operational traceability.

What steps are required to start an end-to-end code ship process?

To start an end-to-end code ship process, you request a release to trigger the workflow. The automation then performs base-branch detection, runs tests, bumps the version, updates the changelog, commits, pushes, and returns a PR URL.