What problem does it solve?
Shipping code requires many manual, error-prone steps: merging the base branch, running tests against the merged state, bumping the version, updating the changelog, committing, pushing, and opening a pull request. Mistakes or missed steps cause broken releases, flaky CI, and wasted review cycles.
Core Features & Use Cases
- End-to-end ship workflow: Merge the base branch into your feature branch, run test suites, and surface failures or merge conflicts before landing.
- Release hygiene: Bump semantic VERSION, update CHANGELOG from the diff, commit structured changes, and push a clean, auditable PR.
- Gating & reviews: Run automated pre-landing reviews, enforce eng-review gates, and stop for human decisions on major version bumps or unresolved conflicts.
- Use case: From a finished feature branch, run the skill to produce a tested, versioned PR ready for CI and reviewers without manually juggling merges and changelog edits.
Quick Start
Run /ship from your feature branch to merge the base, run tests, bump VERSION, update CHANGELOG, commit, push, and open a pull request.