ship

Automate Git code shipping from branch merge to pull request creation.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill ship-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill ship-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code manually is error-prone and inconsistent. This skill automates the entire release workflow from merging the base branch to creating a pull request, ensuring tests pass, versions are bumped, and changelogs are updated without missing steps.

Core Features & Use Cases

  • Automated Merge & Test: Detects the base branch, merges it, and runs the test suite to catch conflicts or failures early.
  • Version & Changelog Management: Automatically bumps the VERSION file and updates CHANGELOG based on recent commits.
  • Safe PR Creation: Reviews the diff, commits changes with a standardized message, pushes to the remote, and opens a pull request.
  • Use Case: A developer who just finished a feature can simply ask to "ship it" and trust that the code is merged, tested, documented, and ready for review without running a dozen manual git commands.

Quick Start

Use the ship skill to merge the current branch, run tests, update the version and changelog, and create a pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git merge, test, and pull request creation for a feature branch?

Automating git workflow involves detecting the base branch, merging it, running tests, bumping versions, updating changelogs, and opening a pull request. This skill executes that entire sequence safely to ensure code is tested and documented before review.

What's the best way to update a changelog and bump versions before opening a pull request?

The best way to manage version bumps and changelog updates is to parse recent git commits and automatically write changes to the VERSION and CHANGELOG files. This ensures release documentation is consistent before pushing to the remote repository.

How does automatic base branch detection work when merging a feature branch?

Automatic base branch detection identifies the target integration branch so the feature branch can be safely merged. After detection, the skill merges the base branch and runs the test suite to catch conflicts or failures early in the release workflow.

Do I need GitHub or GitLab authentication to automate pull request creation?

GitHub or GitLab authentication is optional but required for remote operations like opening pull requests. Git CLI access and Bash execution permissions are mandatory for local operations like merging branches, running tests, and updating version files.

Why should I automate the code shipping workflow instead of running git commands manually?

Manual code shipping is error-prone and inconsistent, often missing steps like changelog updates or test runs. Automating the release workflow ensures tests pass, versions bump correctly, and pull requests open with standardized commit messages.

Can I run test suites and review diffs before pushing to the remote repository?

Yes, the workflow merges the base branch, runs the test suite, reviews the diff, and commits changes before pushing to the remote. This ensures only tested and verified code is pushed for pull request creation.