ship

Orchestrate the end-to-end ship workflow from base-branch merge to PR creation.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill ship-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/ship
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill ship-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automates the complete release workflow, combining base-branch detection, test execution, diff review, version bumping, CHANGELOG updates, commits, pushes, and PR creation into a repeatable, auditable process.

Core Features & Use Cases

  • Orchestrates the full shipping pipeline from local repo to PR on your hosting platform.
  • Bumps version numbers, updates CHANGELOG, and pushes changes with a single command.
  • Handles plan-mode safety, routing prompts, and post-merge documentation updates.

Quick Start

Run the ship skill to release the current branch and generate a PR with version bump.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git pull request creation and version bumping in one step?

To automate pull request creation and version bumping together, you can use an end-to-end ship workflow that merges the base branch, runs tests, bumps the VERSION, updates the CHANGELOG, commits, pushes, and generates the PR automatically.

What is the best way to keep a CHANGELOG updated automatically before opening a PR?

Keeping a CHANGELOG updated automatically before opening a PR is handled by release automation that reviews branch diffs, applies a version bump, appends changelog entries, commits the changes, and pushes them alongside the PR creation.

How does an automated release workflow handle base branch detection before running tests?

An automated release workflow handles base branch detection by identifying the target integration branch, merging it into the current working branch, and then executing the test suite to ensure the pull request is ready for review.

Can I use automated PR readiness workflows with standard CLI git tools?

Yes, you can use automated PR readiness workflows with standard CLI git tools. The process relies on standard command-line interfaces for git operations and the host platform's PR client to manage pushes and pull request generation.

Do I need a specific CI pipeline to automate version bumps and pull request generation locally?

You do not need a specific CI pipeline to automate version bumps and pull request generation locally. The workflow integrates with common PR pipelines but relies on local scripts and standard CLI tools to manage the release sequence.

When should I not use end-to-end shipping automation for my git project?

You should not use end-to-end shipping automation for git projects lacking a repeatable release process. The workflow is designed for structured projects requiring auditable version bumps, changelog updates, and consistent pull request generation.