ship

Merge base branches, run tests, bump versions, and create pull requests.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill ship-jonkiky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/ship
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill ship-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end shipping workflow from base-branch merge through tests, changelog updates, and PR creation to deployment readiness.

Core Features & Use Cases

  • Detects the base branch, merges changes, runs tests, reviews diffs, bumps the version, updates the CHANGELOG, commits, pushes, and opens a PR.
  • Proactively orchestrates shipping when the user requests deployment or a PR, without pushing or merging directly.
  • Use when you want a reproducible release flow that moves code from feature branches to production with traceability.

Quick Start

Merge the base branch, run tests, update version, update changelog, commit, push, and open a PR for deployment.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git merge, tests, and PR creation for a release?

To automate git merge, tests, and PR creation for a release, this Skill orchestrates the workflow: it detects the base branch, merges changes, runs tests, updates the changelog, and opens a pull request without directly pushing or merging.

What is the best way to bump VERSION and update CHANGELOG before deploying?

The best way to bump VERSION and update CHANGELOG before deploying is using an automated shipping workflow that reviews diffs, applies versioning, records changelog updates, commits, and pushes the changes to create a PR.

Does this release workflow push code directly to the base branch?

No, this release workflow does not push code directly to the base branch. It proactively orchestrates shipping by preparing the feature branch, running tests, and creating a PR for review instead of merging directly.

Can I use this to move code from feature branches to production with traceability?

Yes, you can use this to move code from feature branches to production with traceability. It provides a reproducible release flow that automates merging, testing, versioning, and PR creation for deployment readiness.

Why should I use an automated end-to-end shipping workflow for versioning?

You should use an automated end-to-end shipping workflow for versioning to ensure a reproducible release flow. It eliminates manual steps by automatically detecting the base branch, running tests, updating the CHANGELOG, and creating PRs.