git-commit_skill

Overview

This skill generates well-structured Git commit messages by combining Conventional Commits with Gitmoji. It enforces a consistent, readable history that makes intent and scope clear for reviewers and automation.

How this skill works

Inspect staged changes and choose a commit type and matching Gitmoji (e.g., ✨ feat, 🐛 fix, 📝 docs). Compose messages in the format: <gitmoji> <type>(<scope>): <subject> followed by an optional body and footer for additional context or issue references. The skill enforces rules for tense, capitalization, length, and placement of breaking changes.

When to use it

• When creating commits for code, docs, tests, or configuration changes
• When the repository requires a consistent commit format for CI/CD or changelogs
• When you want commit messages to clearly communicate what and why
• Before pushing changes to shared branches or opening pull requests
• When automated tools parse commit messages to generate releases

Best practices

• Run git diff --staged to review changes before composing a message
• Pick the single most appropriate type and include a Gitmoji to visualize intent
• Keep the subject under 50 characters, imperative present tense, no trailing period
• Use scope to indicate the affected module (api, auth, chat) when helpful
• Add a body to explain reasoning or design trade-offs; use the footer for issues or BREAKING CHANGE

Example use cases

• Committing a new feature: ✨ feat(auth): add password reset via email
• Fixing a bug that caused crashes: 🐛 fix(api): handle null user in session middleware
• Updating documentation: 📝 docs(readme): document setup and env variables
• Refactoring code for maintainability: ♻️ refactor(cache): simplify eviction logic
• Tagging a release: 🔖 release: v1.2.0