ship

Generate conventional commit messages and execute the full Git workflow.

4|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/missuo/ship --skill ship-missuo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/missuo/ship/tree/main
Command: npx skills add https://github.com/missuo/ship --skill ship-missuo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire Git commit and push process, including intelligent commit message generation, saving developers time and ensuring consistent commit history.

Core Features & Use Cases

  • Automatic Commit Type Inference: Detects commit types (feat, fix, docs, etc.) based on file changes.
  • Smart Scope Detection: Extracts commit scopes from file paths.
  • Full Git Workflow: Stages, commits, and pushes changes in one command.
  • Safety Checks: Warns about sensitive files and large changes.
  • Use Case: After making several bug fixes and adding a small feature, you can invoke /ship to have the Skill automatically stage, commit with a well-formatted conventional commit message, and push your changes.

Quick Start

Use the ship skill to commit and push your current git changes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate generating conventional commit messages for my Git workflow?

You can automate conventional commit message generation by analyzing file changes to infer commit types like feat or fix, extracting scopes from file paths, and executing the full Git workflow from staging to pushing.

Can I automatically stage and push my code changes in one command?

Yes, you can automatically stage and push code changes in one command. The Skill executes the full Git workflow, taking your local modifications from staging through committing with an intelligent message, and finally pushing them to the remote repository.

How does automatic commit type inference work for conventional commits?

Automatic commit type inference works by analyzing your staged file changes to determine the appropriate conventional commit type, supporting categories including feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert.

Are there safety checks for sensitive files when automating Git commits?

Yes, there are safety checks for sensitive files when automating Git commits. The Skill includes built-in warnings for sensitive files and large changes to prevent accidental exposure or overwhelming pull requests during the automated workflow.

What is the best way to ensure consistent conventional commit history without manual typing?

The best way to ensure consistent conventional commit history is to automate message generation and the staging-to-push workflow. This approach infers commit types and scopes from file changes, saving time and enforcing formatting consistency.