Commit and Push Workflow
Steps
- •Analyze changes: Run
git statusandgit diffto see all modified/untracked files - •Group related files: Files belonging to the same feature go in one commit, unrelated files get separate commits
- •For each commit group:
- •Select emoji prefix based on change type
- •Write concise English commit message
- •Stage files:
git add <files> - •Commit (no Claude attribution)
- •Push all commits to remote
Emoji Prefixes
| Emoji | Type |
|---|---|
| ✨ | New feature |
| 🐛 | Bug fix |
| 📝 | Documentation |
| ♻️ | Refactoring |
| 🎨 | Styling/formatting |
| ⚡ | Performance |
| 🔒 | Security |
| 🧪 | Tests |
| 🔖 | Version bump |
| 🚀 | Deployment |
| ⚙️ | Configuration |
| 🗑️ | Remove code/files |
Commit Message Format
code
<emoji> <Short description in English>
Example: ✨ Add return deadline display to product detail page
Rules
- •English only for commit messages
- •No Claude attribution (no "Co-Authored-By" or "Generated with Claude")
- •Group related files (component + styles + utils for same feature = one commit)
- •Separate unrelated changes into different commits
- •Use HEREDOC for commit messages to handle special characters