ship

Name: ship
Availability: InStock
Author: howdeploy

Automate the end-to-end ship workflow from branch to PR.

15|1|Updated Apr 4, 2026

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

Ready to run

npx skills add https://github.com/howdeploy/NekoFree --skill ship-howdeploy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/ship
Command: npx skills add https://github.com/howdeploy/NekoFree --skill ship-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge and deploy are often the parts that slow teams down. This Skill coordinates the entire ship workflow so code changes move from branch to production with fewer handoffs and fewer mistakes.

Core Features & Use Cases

End-to-end ship workflow orchestration: detect base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create PR.
Proactive or on-demand invocation: trigger the ship flow when user asks to ship or when readiness is detected.
Safe, auditable changes: records actions and creates PRs to preserve code history and review.

Quick Start

Ship the current feature branch to main by running tests, merging changes, bumping versions, updating the changelog, 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 git pull requests and version bumps in a CI/CD pipeline?▼

Automating git pull requests and version bumps involves orchestrating an end-to-end ship workflow that detects the base branch, runs tests, reviews diffs, bumps versions, updates changelogs, and creates PRs automatically within your CI/CD pipeline.

What is an end-to-end ship workflow for code changes?▼

An end-to-end ship workflow orchestrates the full deployment cycle: detecting the base branch, running tests, reviewing diffs, bumping the VERSION file, updating the CHANGELOG, committing, pushing, and opening a pull request to ensure safe, auditable changes.

How do I trigger an automated branch merge and push to main?▼

You can trigger an automated branch merge and push to main by asking to ship, deploy, or create a PR. The workflow can also proactively invoke when code readiness is detected, safely merging changes and opening a pull request.

Does automated diff review work before creating a pull request?▼

Yes, automated diff review runs before creating a pull request. The workflow reviews code diffs, records actions to preserve history, and ensures safe, auditable changes are made before pushing the branch and opening the PR.

Can I use this automated ship workflow without setting up dependencies?▼

You can use this automated ship workflow without setting up dependencies because it operates with no external dependencies, applying deterministic tool usage to gate steps like test runs, version bumps, and pull request creation.

When should I avoid automating the code deployment workflow?▼

You should avoid automating the code deployment workflow if your project requires manual review gates outside of standard pull requests, as this workflow focuses on automating deterministic steps like tests, version bumps, and PR creation for moving code to production.