ship

Automate release management with version bumps, changelog updates, and git tags.

1|Updated Aug 21, 2025

Search Tags:#automation #git #changelog #release #ci-cd #tag #version-bump

Ready to run

npx skills add https://github.com/camronh/EZVals --skill ship-camronh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/camronh/EZVals/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/camronh/EZVals --skill ship-camronh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing software from dev to main can be error-prone and time-consuming; this Skill automates the release workflow to ensure consistent versioning, changelog updates, and timely tagging.

Core Features & Use Cases

End-to-end release automation: validates dev branch, runs tests, bumps version, updates changelog, and creates git tags.
Guardrails and visibility: asserts test success, updates docs/metadata, and provides a repeatable release pattern for teams.
Use Case: When preparing a new software release, trigger this Skill to produce a clean commit set on main with a version bump and a published tag.

Quick Start

Run the release workflow on the dev branch to create a new version and tag.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate version bumps and changelog updates for git releases?▼

Git release automation handles version bumps, changelog updates, and tag creation end-to-end. It validates the dev branch, runs tests, and commits synced version metadata across files like pyproject.toml before pushing tags to main.

What is the dev to main release workflow for syncing version metadata?▼

The dev to main release workflow merges feature branches by running tests, updating docs and changelogs, bumping pyproject.toml versions, amending metadata comments, and creating a clean git tag commit set on the main branch.

Can I use automated release management to update docs and run tests before tagging?▼

Yes, automated release management asserts test success and updates documentation before tagging. It provides guardrails by safely aborting the release process if tests fail or error checks detect metadata sync issues across files.

Does this release automation tool work with pyproject.toml and changelog files?▼

Yes, this release automation reads and updates docs/changelog.mdx, bumps the pyproject.toml version, and amends version comments in skill metadata files to ensure all version references are synced before creating the git tag.

What happens if tests fail during an automated version bump and git tag workflow?▼

If tests fail during the version bump workflow, the automation includes error checks that trigger a safe abort. This prevents incomplete commits, unsynced version metadata, or invalid git tags from being pushed to the main branch.

What's the best way to ensure consistent versioning and tagging across multi-step release workflows?▼

The best way to ensure consistent versioning is using an end-to-end release automation pattern. It standardizes the multi-step workflow of bumping versions, updating changelogs, syncing metadata, and creating git tags to eliminate manual release errors.