skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Merge swarm PRs, cut release candidates, and promote to main.

Updated Apr 17, 2026
Search Tags:#git#release#swarm#tagging#pr-merge#rc
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill ship-smallorbit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/ship
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill ship-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge a completed swarm run into a single release by merging all open swarm PRs into develop, cutting a release candidate, and promoting to main.

Core Features & Use Cases

  • Merges all open swarm PRs into develop to create a cohesive release surface.
  • Cuts a release candidate (RC) on origin/develop and promotes it to main after successful checks.
  • Releases to main with version tagging and closes referenced issues; cleans up RC branches.

Quick Start

Run the ship skill after completing a swarm to merge all open swarm PRs, cut a release candidate, and promote to main.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I merge multiple open swarm PRs into a single release on develop?▼

To merge multiple open swarm PRs into a single release, this skill automates merging all open swarm PRs into the develop branch to create a cohesive release surface before cutting a release candidate.

What is the process to cut a release candidate and promote it to main?▼

Cutting a release candidate involves branching from origin/develop, running deployment readiness checks, and then promoting the verified release candidate to main with final version tagging and issue closure.

How does release orchestration handle merge failures during swarm PR coordination?▼

Swarm release orchestration includes error handling for merge failures during the PR merge phase, ensuring that incomplete or conflicting pull requests are caught before cutting a release candidate.

Do I need a completed swarm run before cutting an RC and promoting to main?▼

Yes, you need a completed swarm run as a prerequisite. The workflow takes all open swarm PRs from that run, merges them into develop, and uses that cohesive state to cut the release candidate.

Can I automate git tagging and issue closure when promoting a release candidate to main?▼

Yes, automating promotion to main includes applying version tagging for the release and automatically closing referenced issues, followed by cleaning up the RC branches.

When should I use an automated swarm release workflow instead of manual git tagging?▼

Use an automated swarm release workflow when you need a single authoritative release from multiple PRs across develop and main, requiring end-to-end orchestration for RC tagging, readiness checks, and final promotion.

Related Skills

Explore More Software Engineering Skills→
jMertajMerta
130

branch-cleaner

Identify and prune stale Git branches locally and on remotes.

Community
Basic
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
mostafa-ismail-2004mostafa-ismail-2004

git-workflow

Guide Git branching, commit, merge, and release decisions for collaborative development.

Community
Advanced