ship

Automate release workflows from feature branch to pull request.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kadenn/kstack --skill ship-kadenn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/kadenn/kstack/tree/main/ship
Command: npx skills add https://github.com/kadenn/kstack --skill ship-kadenn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the end-to-end release workflow by automatically merging, testing, bumping versions, updating changelogs, committing, pushing, and opening PRs.

Core Features & Use Cases

  • Non-interactive, automated ship workflow that runs on a feature branch
  • Auto-detects and executes test commands
  • Handles version bumps and CHANGELOG updates
  • Produces a PR ready for review

Quick Start

Run /ship to execute the fully automated ship workflow from your feature branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my release workflow from a feature branch to a pull request?

Automating your release workflow from a feature branch involves running a single command to handle pre-landing checks, version increments, changelog updates, and PR creation. This process operates non-interactively to seamlessly push committed changes and return a review-ready pull request URL.

Can I automatically resolve merge conflicts during an automated pull request workflow?

Yes, the automated pull request workflow can resolve simple merge conflicts automatically. It integrates conflict resolution into the end-to-end ship process before executing tests, bumping the version, and committing changes to the remote origin.

What is the best way to manage version bumps and changelog updates before opening a PR?

The best way to manage version bumps and changelog updates before opening a PR is through an automated non-interactive workflow. It detects test commands, increments the VERSION file, updates the CHANGELOG, commits the changes, and produces a final PR ready for review.

Does the automated ship workflow require manual test command configuration?

No, the automated ship workflow does not require manual test command configuration. It auto-detects and executes the appropriate test commands as part of its end-to-end pre-landing checks before incrementing the version and pushing to origin.

When should I use an automated release workflow instead of manually creating pull requests?

You should use an automated release workflow for collaborative software projects requiring consistent pre-landing checks, version management, and changelog updates. It replaces manual PR creation by resolving simple conflicts, running tests, and pushing changes non-interactively to streamline releases.

Why does my automated version bump workflow fail during non-interactive pull request creation?

An automated version bump workflow may fail during non-interactive pull request creation if pre-landing checks encounter unresolved complex merge conflicts or if test commands fail. The workflow requires successful test execution and clean conflict resolution before committing and pushing changes.