ship

Detect the base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill ship-makyua-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill ship-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship workflow automates the end-to-end release process by detecting the base branch, running tests, reviewing diffs, bumping the VERSION, updating the changelog, and creating a PR. It helps teams ship reliably without manual handoffs.

Core Features & Use Cases

  • Detects the base branch, runs tests, reviews diffs, bumps the VERSION, updates the CHANGELOG, commits, pushes, and creates a PR.
  • Proactively invokes the ship flow when users indicate readiness to deploy or want a PR created, ensuring a consistent release process.
  • Integrates with standard Git workflows and CI tooling to reduce manual coordination and speed up releases.

Quick Start

Tell me to ship when your code is ready, and I will execute the full automated ship workflow.

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 creating a pull request?

Automated git release workflows handle end-to-end shipping by detecting the base branch, running tests, reviewing diffs, bumping the VERSION, updating the CHANGELOG, committing, pushing, and creating a PR.

What is the best way to ship code end-to-end without manual handoffs between testing and pull request creation?

Shipping code end-to-end without manual handoffs is achieved by automating pre-release checks, version bumps, changelog updates, and pull request creation into a single continuous workflow triggered upon release readiness.

How does an automated changelog update and version bump process work before pushing a release?

Automated changelog and version bump processes work by reviewing branch diffs, incrementing the VERSION file, appending changes to the CHANGELOG, and committing these updates before pushing to the remote repository.

Can I trigger an automated pull request creation just by indicating my code is ready to deploy?

Yes, automated pull request creation can be triggered proactively when you indicate readiness to deploy or request a release, executing the full ship workflow without manual coordination.

Do I need standard Git workflows and CI tooling to integrate an automated release process?

Yes, integrating an automated release process requires standard Git workflows and CI tooling to reduce manual coordination, run robust pre-release checks, and ensure reliable code shipping.

What are the limitations of automating version bumps and changelog updates for Git-based releases?

Limitations of automating Git-based releases involve relying on the accuracy of diff reviews for changelog generation and ensuring test suites are properly configured to pass before the version bump and commit stages execute.