git-commits

What problem does it solves?

Maintaining a clean, readable, and semantically meaningful Git commit history is essential for collaboration, code review, and release management. Inconsistent or vague commit messages hinder understanding and automation. This Skill enforces best practices for Git commits.

Core Features & Use Cases

• Conventional Commits Format: Guidance on the standard format (<type>[optional scope]: <description>) for clear and consistent messages.
• Commit Types: Definitions for common types like feat, fix, docs, refactor, and their semantic versioning implications.
• Atomic Commits: Principles for ensuring each commit represents one logical, independently revertible change.
• Commit Message Rules: Guidelines for imperative mood, line length, and handling breaking changes.
• Claude Code Commit Footer: Specific instructions for including AI-generated attribution in commit messages.
• Use Case: Writing a new feature commit message, fixing a bug and documenting it correctly, ensuring all commits are atomic, or generating a changelog from commit history.

Quick Start

Use the git-commits skill to generate a conventional commit message for a new feature that adds user profile editing.