ship

Automate the end-to-end ship workflow from merge to PR creation.

Updated Apr 26, 2026

Search Tags:#automation #git #versioning #ci-cd #ship #pull-request #tests

Ready to run

npx skills add https://github.com/XinheLIU/human-leverage --skill ship-xinheliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill ship-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation eliminates the repetitive, error-prone steps of releasing changes: merging base branches, running test suites, reviewing diffs, bumping versions, updating CHANGELOGs, committing, pushing, and creating PRs.

Core Features & Use Cases

Automates the end-to-end shipping workflow: merge base, run tests, update version, refresh changelog, commit changes, push, and open a PR.
Proactively suggests when the user’s code appears ready to ship or when deployment actions are appropriate.
Use Case: When finishing a feature, trigger the ship workflow to produce a clean PR with all checks passing.

Quick Start

Ship the current feature branch by merging from the base, running tests, updating version and changelog, committing, and opening a PR.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate creating a pull request with version bump and changelog updates?▼

Automated pull request creation handles the end-to-end ship workflow by merging the base branch, running tests, bumping the VERSION file, updating the CHANGELOG, and opening a PR. This eliminates repetitive manual git operations and ensures traceable deployment history.

What is the best way to ensure my feature branch passes tests before pushing to main?▼

Running tests before pushing to main is handled automatically by the ship workflow, which executes your test suite after merging the base branch and before committing changes. This multi-step validation ensures only tested code enters your pull request.

Can I trigger a git deploy and PR creation workflow just by asking to ship code?▼

Yes, the ship workflow activates when you ask to ship, deploy, push to main, or create a PR. It proactively suggests deployment actions when your code is ready, automating git operations, changelog updates, and pull request generation.

Does automated PR creation work without additional CI-CD dependencies?▼

Yes, automated PR creation operates with zero dependencies, using deterministic git operations to merge branches, run tests, update versions, and push changes. It functions independently without requiring external CI-CD pipeline integrations.

Why does my automated ship workflow update the CHANGELOG and VERSION files?▼

Updating the CHANGELOG and VERSION files ensures traceable history and semantic versioning during the ship workflow. This automated documentation creates a clean, reviewable pull request with clear deployment records for every feature shipped.

When should I avoid using an automated git workflow for pull request creation?▼

Avoid automated pull request creation when your project requires manual review of git diffs before committing, or when custom deployment steps outside standard versioning, changelog updates, and test validation are needed for your specific release pipeline.