productionos-ship

Automate release preparation by validating changes, updating version metadata, and creating PRs.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: productionos-ship
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/codex-skills/productionos-ship
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code safely requires coordinating base-branch synchronization, validation, version bumps, changelog updates, and PR automation to minimize risk and speed releases.

Core Features & Use Cases

  • Base-branch detection and synchronization: aligns feature branches with their base to ensure clean merges.
  • Validation & testing: runs tests and type checks to guarantee release readiness.
  • Release metadata updates: bumps VERSION, updates CHANGELOG, and records release notes.
  • PR creation & push: commits changes, pushes to remote, and opens or updates a PR. Use case: A feature branch on a long-running release train is prepared for merge by automatically validating changes and creating a PR with release notes.

Quick Start

Run the ship workflow on your current branch to prepare, validate, and open a PR for release.

Frequently Asked Questions about productionos-ship

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

FAQPage Schema
How do I automate pull request creation and version bumping for a feature branch?

Automating pull request creation and version bumping involves synchronizing your feature branch with its base, running validation tests, updating the VERSION and CHANGELOG files, and automatically pushing the changes to open a release-ready PR.

What is the best way to synchronize a feature branch with a base branch before creating a PR?

The best way to synchronize a feature branch with a base branch is to perform an automated base-branch resolution that safely merges or rebases changes, ensuring your feature branch is aligned and clean before opening a pull request.

How do I ensure my code is release-ready before pushing a pull request?

To ensure code is release-ready before pushing a pull request, run automated validation and testing workflows that execute type checks and tests, verifying that your branch changes satisfy release requirements without breaking existing functionality.

Can I automatically update the changelog and release notes when preparing a pull request?

Yes, you can automatically update the changelog and release notes during the shipping workflow, which records release metadata and commits these updates directly to the feature branch before opening the pull request.

Does this automated shipping workflow work with long-running release trains?

Yes, this automated shipping workflow works with long-running release trains by resolving the base branch, validating changes, bumping versions, and opening PRs that safely prepare feature branches for merge into the release train.

Why do I need to synchronize with the base branch before opening a release pull request?

You need to synchronize with the base branch before opening a release pull request to guarantee a clean merge, preventing conflicts and ensuring the automated validation tests run against the most current codebase state.