skills.rest
jm199seo
jm199seoCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate Git release shipping by merging base branch, testing, updating CHANGELOG, bumping VERSION, and creating a PR.

Updated Mar 22, 2026
Search Tags:#automation#git#changelog#release#pr#ship
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill ship-jm199seo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill ship-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating code shipping involves merging base branches, running tests, reviewing diffs, bumping versions, updating changelogs, committing, pushing, and creating PRs. This Skill automates the entire release workflow to reduce manual toil and minimize release errors.

Core Features & Use Cases

  • Automatic base-branch detection and merge
  • Running tests across the project and reporting failures
  • Bumping version numbers and updating CHANGELOG
  • Committing changes, pushing branches, and opening PRs
  • Proactive suggestions when code is ready or deployment is requested

Quick Start

Run the ship workflow to automatically merge the base branch, run tests, update CHANGELOG, bump versions, and open 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 my git release workflow from running tests to creating a PR?▼

You can automate your git release workflow by triggering the ship command, which automatically merges the base branch, runs tests, bumps the VERSION, updates the CHANGELOG, and creates a PR.

What is the best way to update the changelog and bump version numbers before pushing to main?▼

The best way to update changelogs and bump versions is to use an automated release workflow that detects the base branch, applies version increments, generates changelog entries, and commits changes before pushing.

Can I automatically run tests and review diffs before opening a pull request?▼

Yes, automated shipping workflows can run tests across your project and review diffs before committing changes and opening a pull request, ensuring code readiness.

Does the automated PR creation process support proactive suggestions when code is ready for deployment?▼

Yes, the automated PR creation process supports proactive suggestions, prompting you to ship, deploy, push to main, or create a PR when it detects code is ready for release.

What are the limitations of automating end-to-end release shipping with git workflows?▼

A limitation of automating end-to-end release shipping is that it depends on successful test execution; if tests fail, the workflow reports failures and halts the automated merge, commit, and PR creation process.

Do I need manual base-branch detection to merge and push code for a release?▼

No, you do not need manual base-branch detection; the automated shipping workflow detects the base branch automatically to merge changes, update files, and push branches for release.

Related Skills

Explore More Software Engineering Skills→
kirvinkirvin

sync

Fetch upstream changes and rebase the current Git branch onto them.

Community
Intermediate
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
fivebucksventuresfivebucksventures

commit-to-git

Stage changes, bump patch version, commit, push, and tag releases.

Official
Advanced