ship

Automate release workflows from branch merge to PR creation.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apeejay-education/cadencesprout --skill ship-apeejay-education
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill ship-apeejay-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release process: detect the base branch, merge changes, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR, reducing manual toil and scope errors.

Core Features & Use Cases

  • End-to-end shipping: automatically merge base branch, run tests, review diffs, bump versions, and open a PR for deployment.
  • Proactive deployment readiness: suggests when code is ready to push to main and deploy, improving release confidence.
  • Use Case: On a feature branch, you run ship to produce a ready-to-merge PR with updated changelog and version bump, ready for review.

Quick Start

Ship changes by running the ship workflow on your feature branch to prepare a release candidate.

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 branch merge to PR creation?▼

To automate your git release workflow, you can use a tool that detects the base branch, merges changes, runs tests, bumps versions, updates the changelog, and opens a PR. This reduces manual toil and scope errors during deployment.

What is the best way to bump version and update changelog before opening a PR?▼

The best way to bump versions and update changelogs is to run an end-to-end shipping process on your feature branch. This automatically prepares a release candidate with updated metadata, ready for review and merge.

How do I prepare a release candidate on a feature branch for deployment?▼

You prepare a release candidate on a feature branch by running a ship workflow. This merges the base branch, reviews diffs, bumps the VERSION, updates the CHANGELOG, commits, pushes, and creates a ready-to-merge PR.

Does automated shipping require CI integration and merge permissions?▼

Yes, automated shipping requires access to a Git repository with merge permissions and CI integration. This ensures tests and builds run automatically before a PR is created, maintaining release confidence.

Can I suggest when code is ready to push to main and deploy?▼

Yes, proactive deployment readiness suggests when code is ready to push to main and deploy. This improves release confidence by ensuring the end-to-end release process is complete before deployment.