--- name: git-commit description: A skill for writing Git commit messages. It follows rules combining Conventional Commits and Gitmoji to maintain a consistent commit history. --- # Git Commit Message Convention Utilize this skill when writing Git commit messages to apply Conventional Commits rules and Gitmoji. ## When to Use This Skill Activate this skill in the following situations: - When committing code changes - When a commit message format is required - When you need to maintain a consistent commit history ## How to Write Commit Messages ### Step 1: Check Staged Changes Check the staged changes using the `git diff --staged` command. ### Step 2: Determine Commit Type Select the appropriate type and Gitmoji for the changes: | Gitmoji | Code | Type | Description | | :-----: | :------------------: | :--------- | :-------------------------------------- | | ✨ | `:sparkles:` | `feat` | Add a new feature | | 🐛 | `:bug:` | `fix` | Fix a bug | | 📝 | `:memo:` | `docs` | Add or update documentation | | 🎨 | `:art:` | `style` | Code formatting, structural improvement | | ♻️ | `:recycle:` | `refactor` | Code refactoring | | ✅ | `:white_check_mark:` | `test` | Add or update test code | | 🔧 | `:wrench:` | `chore` | Update build, config files, etc. | | 🚀 | `:rocket:` | `perf` | Improve performance | | 🔖 | `:bookmark:` | `release` | Version release | > Always check this: [gitmoji | An emoji guide for your commit messages](https://gitmoji.dev/) ### Step 3: Compose the Message Compose the commit message in the following format: ```text ():