ship-git-commits

Enforce atomic Git commits with a type, scope, and description format.

9|3|Updated Feb 26, 2026

Search Tags:#git #version control #code history #commits #atomic commits #convention

Ready to run

npx skills add https://github.com/dilhanz/ship --skill ship-git-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship-git-commits
Source: https://github.com/dilhanz/ship/tree/main/.claude/skills/ship-git-commits
Command: npx skills add https://github.com/dilhanz/ship --skill ship-git-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a consistent and informative Git commit message format, making it easier to understand the history and purpose of changes in a codebase.

Core Features & Use Cases

Atomic Commits: Ensures each commit represents a single, verifiable task.
Standardized Format: Adheres to a clear <type>(<feature-name>): <description> structure.
Use Case: When implementing a new user authentication feature, commits like feat(user-auth): add user model with prisma schema and fix(user-auth): handle expired token edge case clearly communicate the nature and scope of each change.

Quick Start

Use the ship-git-commits skill to format your next commit message.

Frequently Asked Questions about ship-git-commits

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

FAQPage Schema

How do I format Git commits for a feature development workflow?▼

Format Git commits using the structure `<type>(<feature-name>): <description>` with an imperative description to standardize code history and improve auditability.

What are atomic Git commits and when do I need them?▼

Atomic Git commits ensure each commit represents a single, verifiable task. You need them to maintain a structured and auditable codebase history during feature development.

What is the best way to structure commit messages for code automation?▼

Structure commit messages for code automation by applying a standardized format with type, scope, and imperative descriptions, which enables clear communication of change nature and scope.

Can I use a standardized commit convention for existing version control projects?▼

Yes, you can apply standardized commit conventions to existing version control projects requiring a structured history. It uses type and feature-name scopes to clarify the purpose of changes.

Why enforce a specific format for Git commit history?▼

Enforcing a specific format for Git commit history solves the problem of unclear changes by making it easier to understand the purpose and nature of codebase modifications.