ship

Automate release workflows with merges, tests, version bumps, and PR creation.

2|Updated Dec 8, 2018
One-click install
npx skills add https://github.com/indykish/dotfiles --skill ship-indykish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/indykish/dotfiles/tree/main/skills/ship
Command: npx skills add https://github.com/indykish/dotfiles --skill ship-indykish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship orchestration automates the end-to-end release workflow: merging main, running tests, evaluating changes, bumping versions, updating changelogs, committing, pushing, and opening a PR.

Core Features & Use Cases

  • Pre-flight checks to ensure the branch is ready for release.
  • Automated merge of origin/main, test execution (parallel), diff review, and PR generation.
  • Version bump decisions and changelog generation with deterministic commits.

Quick Start

Execute /ship on a feature branch to start the automated release process.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git release workflow from running tests to opening a pull request?▼

To automate a git release workflow, you can orchestrate merges, parallel test execution, version bumps, changelog updates, and PR creation from a feature branch. This ensures pre-merge gating and CI-aware validation before pushing code.

What is an end-to-end ship workflow for feature branches?▼

An end-to-end ship workflow is an automated release process that merges origin/main, runs pre-flight checks, evaluates diffs, bumps versions, generates changelogs, and drafts a pull request. It targets feature branches to enable deterministic release artifacts.

How do I generate changelog updates and version bumps automatically before merging?▼

You can generate changelog updates and version bumps automatically by applying version decision logic and diff analysis to your feature branch. This creates deterministic commits that document changes before opening a pull request.

Can I run parallel tests and pre-flight checks before creating a pull request?▼

Yes, you can run parallel test execution and pre-flight checks before PR creation. The workflow validates your feature branch with CI-aware checks to ensure it is fully ready for release before pushing.

Does automated release workflow orchestration work without external CI dependencies?▼

Yes, automated release workflow orchestration operates without external dependencies. It implements internal pre-flight checks, git operations, and diff analysis to handle merges, tests, and PR drafting independently.

Why use deterministic commits in an automated PR generation workflow?▼

Deterministic commits ensure consistent, traceable release artifacts during automated PR generation. By standardizing version bumps and changelog updates, the workflow prevents manual errors and maintains a predictable git history.