ship

Automates end-to-end release workflows from change detection to PR creation.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/yolopunk/jedi --skill ship-yolopunk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/yolopunk/jedi --skill ship-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate the end-to-end release process by detecting base changes, running tests, bumping versions, updating CHANGELOG, committing, pushing, and creating pull requests to ship code safely and consistently.

Core Features & Use Cases

  • End-to-end release orchestration across branches with minimal manual steps.
  • Automatic version bumps and CHANGELOG updates aligned with semantic conventions.
  • PR creation and push to remote to accelerate collaboration and code review.

Quick Start

Initiate the ship workflow on your feature branch to automatically detect changes, run tests, bump the version, update the changelog, commit, and open a pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git release workflows with version bumps and pull requests?

To automate git release workflows, you orchestrate change detection, run test scripts, bump semantic versions, update the changelog, and create pull requests to ship code consistently across branches.

What is an end-to-end release orchestration workflow for software projects?

End-to-end release orchestration coordinates detecting base changes, running tests, bumping versions, updating CHANGELOG files, committing, pushing, and opening pull requests to ship code safely and consistently.

Do I need a local git repository and test scripts to automate shipping code?

Yes, automating shipping requires a local git repository with a base branch, properly configured test scripts, and established versioning and changelog conventions to operate safely and execute the release workflow.

How does automatic version bumping and changelog updating work with conventional release processes?

Automatic version bumping and changelog updating works by detecting changes on your feature branch, aligning version increments and CHANGELOG entries with semantic conventions, then committing and pushing those updates to a remote branch.

Can I automate pull request creation and remote pushes for feature branch releases?

Yes, you can automate pull request creation and remote pushes to accelerate collaboration and code review after your feature branch passes tests, receives a version bump, and updates its changelog.

What are the limitations of automating CI/CD shipping workflows without proper versioning conventions?

Without proper versioning and changelog conventions, automated release workflows cannot safely bump versions or update changelogs, risking inconsistent releases and failed automated pull request generation across your branches.