ship

Merge base branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill ship-kakarottoooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/ship
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill ship-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation handles the full release workflow: detect and merge the base branch, run tests, review diffs, bump the VERSION, update the CHANGELOG, commit, push, and create a PR. It also proactively suggests actions when code is ready to deploy.

Core Features & Use Cases

  • Automated release flow: merges the base branch, runs tests, and validates changes before shipping.
  • Versioning & changelog: automatically bumps VERSION and updates CHANGELOG to reflect new releases.
  • PR creation & audit trail: commits changes, pushes to the feature branch, and opens a PR for review, with an auditable history.
  • Proactive guidance: suggests deployment readiness and next steps when the user signals readiness.

Quick Start

Trigger the ship workflow on a feature branch to automatically merge, test, version, 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 my git release workflow from testing to pull request creation?

To automate a git release workflow, the process merges the base branch, runs tests, bumps the version, updates the CHANGELOG, commits, pushes, and opens a pull request for hands-free shipping.

What is the best way to automatically bump versions and update changelogs before opening a PR?

Automated version bumping and CHANGELOG updating occur after tests pass, ensuring the commit pushed to your feature branch and subsequent pull request accurately reflect the new release.

Do I need a configured CI/CD pipeline to automate pull request creation?

You need access to Git, test runners, and a configured PR workflow to automate pull request creation, as the process relies on these environments to validate changes and execute shipping steps.

How does automated base branch merging work during feature branch releases?

Automated base branch merging integrates the latest changes from the main branch into your feature branch before running tests, ensuring release validation occurs against the current codebase.

Can I automate deployment readiness checks for my feature branches?

Deployment readiness checks are automated by running tests and reviewing diffs after merging the base branch, proactively suggesting next steps and deployment actions when code is ready to ship.

What limitations exist when automating end-to-end shipping workflows?

Automating end-to-end shipping workflows requires deterministic steps including base-branch merge, test execution, version bump, and PR creation, limiting flexibility if custom manual interventions are needed during release.