skills.rest
Jesse-L-M
Jesse-L-MCOMMUNITY
Explore all skills by this author →
GitHub

ship

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

Updated Mar 27, 2026
Search Tags:#automation#git#ci/cd#release-management#ship#pull-request
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill ship-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill ship-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual shipping pipelines are error-prone and slow. This Skill automates the complete publish workflow so code goes from changing code to a PR with minimal human taps.

Core Features & Use Cases

  • Detect and merge the base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Run tests and validations end-to-end to ensure quality before shipping.
  • Proactively invoke ship workflows when asked to deploy or create a PR, while still requiring user consent for sensitive steps in some configurations.

Quick Start

Say "ship" to trigger the automated release flow from the current feature branch.

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 pull request workflow from a feature branch?▼

To automate your git pull request workflow, you can trigger an end-to-end ship process that detects the base branch, runs tests, bumps the version, updates the changelog, and opens a PR with minimal manual intervention.

What is the best way to automate release management and version bumping in CI/CD?▼

Automating release management in CI/CD involves detecting the base branch, running validations, automatically bumping the VERSION file, updating the CHANGELOG, and pushing the changes before creating a pull request.

Do I need conventional versioning to automate code shipping and PR creation?▼

Yes, you need conventional versioning in your git repository to automate code shipping. The automated workflow requires a structured version file and access to CI or test commands to successfully bump versions and create pull requests.

How does automated changelog generation work when pushing code to main?▼

Automated changelog generation works by reviewing your code diffs against the base branch, appending the relevant changes to the changelog file, bumping the project version, and committing these updates before pushing to open a PR.

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

Yes, you can run tests and review diffs automatically before opening a pull request. The shipping workflow executes end-to-end test commands and evaluates code diffs to ensure quality validation prior to pushing changes and creating the PR.

Related Skills

Explore More Software Engineering Skills→
kinetaskinetas

ship

Automates the complete ship workflow from base-branch detection to PR creation.

Community
Advanced
StaysrStaysr

version-release

Automate version tagging, changelog generation, and PR workflows for minor and patch releases.

Community
Advanced
greencmgreencm
1

ship

Automate Git code shipping with branch management, tests, and pull requests.

Community
Advanced
tethertotetherto
395

release

Automate NPM package releases by validating versions, updating changelogs, and creating release branches.

Official
Advanced