skills.rest
MFS-code
MFS-codeCOMMUNITY
Explore all skills by this author →
Website𝕏@miguelfsernaGitHub

ship

Automate release PR preparation by merging base branch, running tests, and updating VERSION and CHANGELOG.

8|2|Updated Mar 24, 2026
Search Tags:#testing#changelog#code review#versioning#pull request#release automation#ship
One-click install
npx skills add https://github.com/MFS-code/gstack --skill ship-mfs-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/MFS-code/gstack/tree/main/ship
Command: npx skills add https://github.com/MFS-code/gstack --skill ship-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ship skill turns the risky, multi-step process of preparing a release PR—merging the base branch, running tests, running required reviews, updating versioning and changelogs, and pushing to a PR—into a consistent workflow.

Core Features & Use Cases

  • Fully automated PR creation: Detects the base branch, merges it into your feature branch, and prepares a ready-to-review PR for changes you intend to deploy.
  • Test + review gating: Runs the appropriate test suites and ensures the required engineering review readiness is satisfied before landing.
  • Release hygiene: Handles VERSION and CHANGELOG updates as part of the shipping workflow, then commits and pushes changes to create the PR.

Quick Start

Invoke the ship workflow by typing /ship when you are ready to merge, test, and create a PR for your 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 pull request creation and version updates for a release?▼

Automating pull request creation and version updates involves merging the base branch, running tests, updating the VERSION and CHANGELOG, and pushing changes. The ship workflow coordinates this end-to-end release process with a single command.

What is the best way to ensure my feature branch passes review readiness before merging to main?▼

Ensuring review readiness before merging requires enforcing engineering checks. This workflow automatically aborts on base-branch execution and enforces a review readiness verdict before allowing a feature branch to proceed to pull request creation.

Can I use this release automation to merge the base branch and run tests simultaneously?▼

Yes, you can use release automation to merge the base branch and run tests simultaneously. It detects the base branch, merges it into your feature branch, and executes the appropriate test suites to gate the release before committing.

Does the automated shipping workflow handle CHANGELOG and VERSION file updates for me?▼

Yes, the automated shipping workflow handles CHANGELOG and VERSION file updates for you. It performs release hygiene by updating both files as part of the process, then commits and pushes the changes to create the pull request.

What happens if I trigger the release preparation workflow while on the main base branch?▼

If you trigger the release preparation workflow while on the main base branch, the process automatically aborts. This safety constraint prevents accidental direct commits to the base branch and ensures changes only ship from a feature branch.

Related Skills

Explore More Software Engineering Skills→
CodingCossackCodingCossack
19

finishing-a-development-branch

Validate tests and merge a feature branch into its base branch.

Community
Advanced
1J6K211J6K21

code-review-and-quality

Review code changes across correctness, readability, architecture, security, and performance.

Community
Intermediate
strawgatestrawgate

follow-the-pr

Monitor GitHub pull request states for CI changes, reviews, and merge readiness.

Community
Advanced
onlypfachionlypfachi

ship

Automate merging, testing, version bumping, changelog updates, and PR creation.

Community
Advanced