ship

Orchestrate git operations, test runs, and PR creation for releases.

6|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill ship-himanshu-sangshetti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Himanshu-Sangshetti/cursor-stack/tree/main/ship
Command: npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill ship-himanshu-sangshetti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release engineers need to reliably execute git operations, run tests, and create PRs in a controlled, auditable flow to avoid drift and regressions.

Core Features & Use Cases

  • Structured ship workflow: enforces pre-flight checks, synchronized main, and automated PR creation.
  • Deterministic execution: executes defined steps in order to land changes safely.
  • Audit-friendly: provides clear diffs, test results, and reviewer guidance.

Quick Start

Initiate the release flow for the current feature branch by issuing the /ship command and following the guided prompts.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git operations and PR creation for feature branch releases?▼

You can automate disciplined release execution by orchestrating git operations, test runs, and PR creation. The workflow enforces pre-flight checks, synchronizes the main branch, and generates reviewer guidance for auditable handoffs.

What is a disciplined release execution workflow for CI-enabled projects?▼

Disciplined release execution is a deterministic workflow that lands code safely by executing predefined checklists in order. It applies to feature branches and releases, ensuring changes are auditable and regressions are avoided.

How do I run tests and create pull requests in a controlled, auditable flow?▼

To run tests and create pull requests safely, the workflow executes defined steps sequentially, applying pre-flight checks before automated PR creation. It produces deterministic status updates with clear diffs and test results.

Can I override the main branch and test commands in an automated release workflow?▼

Yes, you can override the main branch and test command configurations. The workflow supports these overrides to adapt the predefined release checklist to your specific CI-enabled environment and testing requirements.

Why does my release process suffer from drift and regressions across feature branches?▼

Release drift and regressions occur without a controlled execution flow. Applying a deterministic release workflow with synchronized main branches and enforced pre-flight checks prevents these issues and provides clear audit trails.