mk.ship

Automate commit, PR, and release steps with GitHub integration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mayknxyz/my-kit --skill mk-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mk.ship
Source: https://github.com/mayknxyz/my-kit/tree/main/kit/.claude/skills/mk.ship
Command: npx skills add https://github.com/mayknxyz/my-kit --skill mk-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Shipping code involves coordinating commits, pull requests, release tagging, and changelog updates across multiple tools. This skill streamlines the end-to-end pipeline from feature work to public release by automating the core shipping steps with conventional commits and GitHub integration.

Core Features & Use Cases

  • Automates the three shipping steps: commit creation, PR management, and release publishing.
  • Updates CHANGELOG.md and bumps version data consistently across the workflow.
  • Integrates with GitHub to automate PR creation, merging, and release notes generation.

Quick Start

Ship changes from a feature branch through to release by invoking the ship pipeline on your branch.

Frequently Asked Questions about mk.ship

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

FAQPage Schema
How do I automate conventional commits and GitHub releases from a feature branch?

To automate conventional commits and GitHub releases from a feature branch, you can use a shipping pipeline that orchestrates commit creation, PR management, and release publishing while automatically updating your CHANGELOG.md and bumping versions.

What is the best way to keep CHANGELOG.md updated automatically during a release pipeline?

The best way to keep CHANGELOG.md updated automatically is to use an end-to-end shipping workflow that generates conventional commits and applies automated version bumps directly during the pull request and release publishing steps.

Can I automate pull request creation and merging with conventional commits?

Yes, you can automate pull request creation and merging with conventional commits by integrating a shipping workflow directly with GitHub, allowing the pipeline to handle labeling, PR generation, and release notes without manual intervention.

Does the shipping pipeline require any external dependencies to publish GitHub releases?

No, the shipping pipeline does not require any external dependencies to publish GitHub releases, as it operates independently to orchestrate automated branching, safety checks, and version bumps natively.

When do I need an end-to-end shipping workflow for my repository?

You need an end-to-end shipping workflow when your feature branches require coordinated steps for committing, pulling, and releasing code, ensuring consistent changelog updates and automated release tagging across multiple tools.

Why does my release pipeline fail to generate consistent version bumps across commits?

Your release pipeline might fail to generate consistent version bumps if it lacks an orchestrated shipping workflow that standardizes conventional commits, automatically updates CHANGELOG.md, and applies synchronized version data across all release steps.