yuntan Git Commit
Steps
- Check the recent commit history (
git log -5) and match the language of recent commits (Japanese or English). - Assign every changed hunk to exactly one commit, so that each commit is one logical change. Formatting-only changes get their own commit.
- Write each message in the format below.
Commit Message Format
Based on Conventional Commits 1.0.0. The type table below is authoritative.
<emoji> <type>[(<scope>)][!]: <description>
<body>
[<footer>]
| Emoji | Type |
|---|---|
| ✨ | feat |
| 🐛 | fix |
| ⚡️ | perf |
| ♻️ | refactor |
| 🎨 | style |
| 📝 | docs |
| ✅ | test |
| 🌐 | i18n |
| 🔧 | chore |
| 👷 | ci |
| 📦️ | package |
| 🔖 | version |
| ⏪️ | revert |
| 🔀 | merge |
- Scope: the affected module or top-level directory (e.g.
auth,api,build). Keep it consistent across the project; omit it when a change spans many areas. - Breaking change: append
!after<type>and add aBREAKING CHANGE:footer. Any<type>can carry one. - Description: imperative mood, no trailing period, ~50 chars max.
- Body: explain why, not what (the diff shows what). Wrap at 72 chars.