ship

Automate feature branch landing into main or beta with testing and PR creation.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill ship-vanducng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/vanducng/skills/tree/main/skills/ship
Command: npx skills add https://github.com/vanducng/skills --skill ship-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end landing of a feature branch into official/main or beta/dev targets, including tests, review, versioning, changelog, PR, and release preparation.

Core Features & Use Cases

  • End-to-end branch landing: merges target → test → review → version bump → changelog → commit → push → PR.
  • Supports modes: official (main/master), staging (staging/uat/release), and beta (dev/development/beta).
  • Flags to control flow: --auto, --release, --skip-tests, --skip-review, --skip-pr-comments, --skip-journal, --skip-docs, --dry-run.
  • PR template integration and canonical body generation; automatic verification via CI; optional journaling/docs in background per mode.

Quick Start

Execute the end-to-end ship sequence on a prepared feature branch by choosing a mode (official, staging, or beta) and running the ship command.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate merging a Git feature branch end-to-end with CI verification?

Automating Git feature branch landing involves merging targets, running tests, bumping versions, generating changelogs, and creating PRs while ensuring CI is green before merging. It coordinates these operations end-to-end across official, staging, or beta branches.

What is the best way to prepare a feature branch for an official main release?

Preparing a feature branch for an official main release requires merging the target branch, validating tests, bumping versions, and generating changelog entries. This ensures the branch is reviewed and CI checks pass before final merge and release preparation.

Can I skip tests and code review when landing a Git branch to staging?

Yes, you can skip tests and review when landing a Git branch by using specific flags like --skip-tests and --skip-review. These flags allow bypassing CI verification and review steps for faster staging or beta deployments.

Does this branch landing workflow support beta and development environments?

Yes, the branch landing workflow supports beta and development environments alongside official main merges. It targets dev, development, or beta branches specifically, allowing staging validation and beta previews before official releases.

How do I generate a changelog and pull request body for a feature branch?

Generating a changelog and PR body for a feature branch is handled automatically during the landing sequence. It integrates PR templates and generates canonical bodies to document changes, ensuring proper review and release preparation before pushing.

Why should I use an automated ship command instead of manual Git operations for releases?

Using an automated ship command reduces human error in manual Git operations by coordinating merges, CI verification, versioning, and PR creation sequentially. It enforces CI green checks before merging across modes, ensuring release confidence end-to-end.