skills.rest
CenredJun
CenredJunCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate the end-to-end ship workflow from feature branch to PR.

Updated Mar 27, 2026
Search Tags:#automation#git#workflow#testing#pr#release-management
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill ship-cenredjun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/gstack-ship
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill ship-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship workflow automates the end-to-end release process from a feature branch: merging main, running tests, reviewing diffs, bumping VERSION, updating CHANGELOG, committing, pushing, and creating a PR.

Core Features & Use Cases

  • Deterministic, non-interactive execution that follows a fixed ship workflow.
  • Automated version bumps and CHANGELOG generation to keep releases consistent.
  • PR generation and push to origin, with final PR URL output for quick review.

Quick Start

Trigger the workflow by issuing the /ship command on your 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 workflow from a feature branch to a PR?▼

You can automate the git workflow to a PR by triggering a deterministic ship process that merges main, runs tests, bumps versions, updates the changelog, and pushes to create a PR.

What is the best way to keep release versions and changelogs consistent across pull requests?▼

Automated version bumping and changelog generation during the ship workflow ensures consistent release tracking by updating files deterministically before pushing the final PR.

How does automated release management handle git conflicts when merging main?▼

Automated release management resolves simple conflicts during the main merge step, but it deterministically aborts execution if the workflow is triggered directly on the main branch.

Does the ship workflow run pre-merge checks before creating a pull request?▼

Yes, the ship workflow runs automated pre-merge checks and tests after merging main but before pushing, ensuring the pull request only opens if all validations pass.

How do I start the automated PR creation process after finishing my feature?▼

You start the automated PR creation process by issuing the /ship command on your feature branch, which runs the full workflow and outputs the final PR URL for review.

When should I avoid using an automated branch to PR workflow?▼

You should avoid using an automated branch to PR workflow when you are on the main branch, as the deterministic execution will abort, or when your project requires interactive conflict resolution.

Related Skills

Explore More Software Engineering Skills→
I194I194
9

ship

Automate Git release workflows from branch detection to PR creation.

Community
Advanced
JeffallanJeffallan
10.9k

Code Reviewer

Automate pull request reviews for code quality, security, and maintainability.

Community
Basic
davpatel605-beepdavpatel605-beep

requesting-code-review

Run security scans, quality checks, and independent review workflows before git commits.

Community
Advanced
woosulwoosul

release

Automates git release process with changelog validation and pre-push hooks.

Community
Intermediate