ship

Automate base branch merging, tests, version bumps, changelogs, and pull requests.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill ship-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-ship
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill ship-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the tedious, error-prone manual work of shipping code, including merging base branches, running tests, updating version and changelog files, and creating pull requests, saving development teams significant time and reducing shipping mistakes.

Core Features & Use Cases

  • End-to-End Shipping Automation: Handles base branch detection and merge, test execution, diff review, VERSION bumping, CHANGELOG updates, git commit/push, and PR creation in a single standardized workflow.
  • Proactive Invocation: Automatically triggers when users mention code is ready for deployment, pushing to main, or creating a PR, no manual skill lookup required.
  • Use Case: When your team finishes a feature branch and marks it as ready for production, use this skill to handle all shipping steps without running individual git commands or manually opening a PR.

Quick Start

Use the ship skill to take your current feature branch, run all pre-ship tests, and open a pull request to merge into the main branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git pull request creation and version bumping for a feature branch?

Automating git pull request creation and version bumping requires a standardized code shipping workflow that detects the base branch, executes tests, updates the VERSION file, and pushes the commit before opening the pull request.

What is the best way to streamline code shipping and reduce manual git operations?

Streamlining code shipping involves an end-to-end automation workflow that handles base branch merging, diff review, changelog maintenance, and pull request creation, eliminating manual git operations and reducing human error.

How does automatic changelog maintenance work during code deployment?

Automatic changelog maintenance works by integrating CHANGELOG updates directly into the shipping workflow, appending changes and bumping versions automatically after tests pass and before the final git commit and push.

Do I need to manually trigger the skill when my code is ready for deployment?

No manual trigger is needed for code deployment; the workflow proactively activates when users mention code is ready for deployment, pushing to main, or creating a pull request, handling all shipping steps automatically.

Can I use this to handle base branch merging and test execution before opening a PR?

Yes, you can use this workflow to handle base branch detection and merging, execute pre-ship tests, review the diff, and open a pull request to merge your feature branch into the main branch in a single process.

What are the limitations of automating code shipping workflows for production deployment?

Limitations of automating code shipping workflows include dependency on standardized branch structures for base branch detection and the requirement that all pre-ship tests must pass before version bumping and PR creation can proceed.