ship

Create pull requests or release merges with pre-flight checks and CI integrations.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/fall-out-bug/sdp_lab --skill ship-fall-out-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill ship-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates deployment orchestration by creating PRs to main after feature completion or by merging for releases.

Core Features & Use Cases

  • PR-based deployment: automatically create pull requests to the default branch once a feature is ready or trigger release merges with proper gating.
  • Release automation: bump version numbers, update CHANGELOG, and tag releases for reliable rollouts.
  • Gate checks and reporting: enforce approvals and pre-flight checks, provide deployment status reports.

Quick Start

Invoke @ship with the feature identifier to initiate a PR-based deployment.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pull request creation for feature deployments?

Automate pull request creation by invoking the deployment orchestrator with a feature identifier to automatically open PRs to the main branch once feature work is complete.

How do I automate release merges and version tagging in Git?

Automate Git release merges by triggering release campaigns that bump version numbers, update the CHANGELOG, and tag releases for reliable rollouts.

Can I enforce pre-flight checks and CI integrations before deploying?

Yes, deployment orchestration enforces pre-flight checks and CI integrations by requiring approvals and validating base-branch detection before merging PRs or tagging releases.

What is the best way to manage release campaigns across Git workflows?

Manage release campaigns across Git workflows by automating base-branch detection, PR creation, and release tagging to update deployment artifacts and generate status reports.

Do I need specific CI-CD pipeline configurations to automate deployments?

Deployment automation relies on existing CI-CD pipeline integrations to enforce pre-flight gate checks and provide accurate deployment status reports during PR merges.

Why does automated deployment require base-branch detection?

Automated deployment requires base-branch detection to correctly identify the target default branch, ensuring PRs are created and release merges are routed accurately across Git workflows.