git-commit-practices

What problem does it solve?

Users struggle with messy Git history, large combined commits, and inconsistent messages, leading to difficult code reviews, debugging, and reverts. This skill automates the guidance for maintaining a clean, reviewable, and professional Git history.

Core Features & Use Cases

• Atomic Commit Enforcement: Guides you to make small, single-purpose commits for easier review, safer reverts, and clearer project history.
• Granularity & Frequency: Provides clear rules on when and how often to commit, ensuring no logical change is missed and promoting early, frequent commits.
• Message Quality: Offers templates and guidelines for crafting clear, concise, and imperative commit messages that effectively communicate changes.
• Use Case: When working on a complex feature, this skill proactively reminds you to commit after each logical step (e.g., "Add user authentication data model", "Add user authentication API endpoint") rather than one giant "Add auth feature" commit.

Quick Start

Guide me on best practices for git commits, focusing on granularity and message quality.