ship

Merge the base branch, run tests, and open a PR for release.

43|7|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill ship-lucas-flatwhite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main/ship
Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill ship-lucas-flatwhite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end ship workflow triggered by the /ship command. It handles merging the base branch, executing tests, reviewing diffs, bumping the version, updating the CHANGELOG, committing changes, pushing, and creating a PR.

Core Features & Use Cases

  • End-to-end orchestration: merge base, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Deterministic ships: executes a predefined sequence to ensure release readiness.
  • Use Case: when a feature is ready for release, type /ship to ship to main with a single command.

Quick Start

Trigger the flow by typing /ship to automatically run the ship sequence and open a PR when ready.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git release workflows and PR creation?

Automate git release workflows and PR creation by running a deterministic sequence that merges the base branch, runs tests, bumps versions, updates the changelog, and opens a pull request. Trigger this end-to-end ship workflow with a single /ship command.

What is the best way to merge a base branch, run tests, and open a PR automatically?

The best way to merge a base branch, run tests, and open a PR automatically is using a predefined ship sequence. This deterministic workflow handles base-branch detection, test execution, conflict handling, version bumps, changelog updates, commits, pushes, and final PR creation.

Can I automatically bump versions and update the changelog before pushing a release?

Yes, you can automatically bump versions and update the changelog before pushing a release. The automated ship workflow reviews diffs, applies version increments, updates the CHANGELOG, commits changes, and pushes them before creating the pull request.

Does automated PR creation handle merge conflicts from the base branch?

Automated PR creation includes conflict handling during the base-branch merge step. The workflow detects the base branch, attempts to merge it, and manages conflicts as part of its deterministic release readiness sequence before proceeding to test execution.

Do I need an upstream execution environment to automate ship workflows?

Yes, you need an upstream gstack environment for execution. The automated ship workflow relies on this environment to run its deterministic scripts, record outcomes for auditing, and orchestrate the end-to-end release and PR creation sequence.

Why does my automated release workflow need to record outcomes?

Your automated release workflow records outcomes to provide a reliable audit trail of the deterministic ship sequence. By documenting test execution, conflict handling, version bumps, and PR creation results, the workflow ensures full release readiness visibility.