x-ship

Automate Git release processes with commit squashing, version bumping, changelog generation, and pushing.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/x-mesh/x-kit --skill x-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-ship
Source: https://github.com/x-mesh/x-kit/tree/main/x-kit/skills/ship
Command: npx skills add https://github.com/x-mesh/x-kit --skill x-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process, handling commit squashing, version bumping, changelog generation, and Git repository pushing, saving time and reducing errors in release management.

Core Features & Use Cases

  • Commit Squashing: Automates the process of squashing work-in-progress (WIP) commits into a meaningful release commit.
  • Version Bumping: Automatically increments version numbers based on the type of changes made.
  • Changelog Creation: Generates a changelog from the commit history.
  • Git Pushing: Pushes the release changes to the configured Git repository.
  • Use Case: Use this Skill to streamline the release process for any Git-based project, whether it's a plugin for the x-kit marketplace or a standalone project.

Quick Start

To release a new version, simply execute the command: /xm:ship

Frequently Asked Questions about x-ship

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

FAQPage Schema
How do I automate git release tasks like version bumping and changelog generation?

Git release automation handles commit squashing, version bumping, changelog generation, and Git pushing automatically. You can execute the release process by running the `/xm:ship` command to streamline these tasks for your Git-based project.

What is commit squashing and when do I need it for a release?

Commit squashing consolidates multiple work-in-progress commits into a single, meaningful release commit. It is needed during release automation to maintain a clean and understandable project history before pushing changes to a Git repository.

How does automatic changelog creation from commit history work?

Automatic changelog creation works by analyzing your project's commit history during the release process. It extracts relevant changes and generates a structured changelog file alongside version bumping and commit squashing operations.

Do I need specific Git repository permissions to automate release pushing?

Yes, automating Git pushing requires access to the project's Git repository and associated write permissions. The release automation tool needs these credentials to push the squashed commits, version bumps, and changelogs to the configured remote repository.

Can I use release automation for standalone projects or only marketplace plugins?

You can use release automation for any Git-based project. It streamlines the release process for both standalone projects and marketplace plugins, handling version bumping and changelog generation universally.

What's the best way to squash WIP commits before a version bump?

The best way to squash WIP commits before a version bump is using dedicated release automation. It automatically identifies work-in-progress commits, consolidates them into a meaningful release commit, and proceeds to increment the version number based on the changes made.