ship

Automates Git-based ship workflow including merge, tests, version bump, changelog update, commit, push, and PR creation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/14nethuwa/jrag --skill ship-14nethuwa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/14nethuwa/jrag/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/14nethuwa/jrag --skill ship-14nethuwa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow automation eliminates the manual, error-prone steps required to release code: merging the base branch, running tests, reviewing diffs, bumping versions, updating changelogs, committing, pushing, and creating PRs.

Core Features & Use Cases

  • Automatic base-branch detection and merge into the feature branch to prepare a release branch.
  • Run all tests and lint checks in CI, surface failures early, and halt on blockers.
  • Bump version numbers, update CHANGELOG, commit changes, and push to the remote.
  • Create a PR automatically with a summary of changes, base branch, and target.
  • Proactively suggest shipping actions when code is ready or deployment is requested.

Quick Start

Say '/ship' to start the full automated ship workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git deploy workflow from running tests to creating a pull request?▼

Automating a git deploy workflow involves merging the base branch, running tests, bumping versions, updating the changelog, committing, pushing, and creating a PR. This process eliminates manual release steps and handles merge conflicts with safe fallbacks.

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

The best way to update a changelog and bump a version is to automate the sequence after tests pass. The workflow reviews diffs, applies the version bump, updates the changelog, commits the changes, and pushes to the remote before opening a pull request.

How does automated pull request creation work after merging a base branch?▼

Automated pull request creation works by merging the base branch into the feature branch, running CI checks, and pushing the finalized commits. The system then generates a PR with a summary of changes, base branch, and target.

Can I halt a deployment if CI tests or lint checks fail during the ship process?▼

Yes, you can halt a deployment if CI tests or lint checks fail. The ship workflow surfaces failures early and stops the process on blockers, preventing bad code from being committed, pushed, or submitted as a pull request.

Does the ship workflow handle merge conflicts automatically when preparing a release branch?▼

The ship workflow handles merge conflicts automatically when preparing a release branch by merging the base branch into the feature branch. It includes safe fallbacks to manage edge cases and ensure the deployment process does not break.

When should I use an automated ship workflow instead of manually pushing code to main?▼

You should use an automated ship workflow instead of manually pushing code to main when you want to eliminate error-prone release steps. It proactively suggests shipping actions when code is ready and ensures tests, version bumps, and changelog updates are consistently applied.