ship

Merge base, run tests, update version and changelog, and create a PR.

107|19|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mr-daedalium/ostack --skill ship-mr-daedalium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/mr-daedalium/ostack/tree/main/ship
Command: npx skills add https://github.com/mr-daedalium/ostack --skill ship-mr-daedalium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation to unify the pre-release steps and reduce manual toil across merging, testing, versioning, changelog updates, and PR creation.

Core Features & Use Cases

  • End-to-end shipping workflow: merge base, run tests, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Proactive deployment readiness: suggests when code is ready to ship and guides user through the release.
  • Conflict handling: attempts simple auto-resolutions for common merge conflicts, with safe fallbacks.

Quick Start

Execute the ship workflow on your feature branch to automatically prepare a PR for merge.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate creating a PR from a feature branch with tests and changelog updates?

You can automate the end-to-end shipping workflow by running the ship Skill on your feature branch, which automatically merges the base, executes tests, updates the version and changelog, and creates a PR. This unifies pre-release steps to reduce manual toil.

What is an automated end-to-end git workflow for shipping code?

An end-to-end git shipping workflow unifies merging, testing, versioning, changelog updates, and PR creation into a single automated process. The ship Skill executes pre-flight checks, merges branches, runs tests, bumps versions, and opens pull requests automatically.

Can I automatically resolve merge conflicts when preparing a pull request?

Yes, you can attempt to resolve merge conflicts automatically when preparing a pull request. The ship workflow attempts simple auto-resolutions for common merge conflicts during the base merge step, and includes safe fallbacks if the conflicts cannot be resolved automatically.

Does the automated deployment workflow handle version bumps and changelog generation?

Yes, the automated deployment workflow handles version bumps and changelog generation. During the shipping process, the ship Skill automatically updates the VERSION file and updates the CHANGELOG before committing the changes and pushing them to open a pull request.

What are the limitations of automating git merge conflict resolution during deployment?

The limitation of automating git merge conflict resolution during deployment is that it only attempts simple auto-resolutions for common conflicts. Complex conflicts trigger safe fallbacks, meaning manual intervention may still be required to complete the merge and proceed with the pull request creation.