Git Commit Conventions & Emoji

Why Have Commit Conventions?

Good commit messages let you:

• Quickly understand the purpose of each change
• Auto-generate changelogs
• Make code review and git blame easier
• Keep team collaboration efficient

Commit Message Format

type(scope): description

[optional body]

[optional footer]

Commit Types with Emoji

Commit Process

1. Check for staged changes (git status)
2. If no staged changes, review and stage appropriate files
3. Run pre-commit checks (unless --no-verify)
4. Analyze changes to determine commit type
5. Generate descriptive commit message
6. Include scope if applicable: type(scope): description
7. Add body for complex changes explaining why
8. Execute commit

Best Practices

• Keep commits atomic and focused
• Write in imperative mood ("Add feature" not "Added feature")
• Explain why, not just what
• Reference issues/PRs when relevant
• Split unrelated changes into separate commits

Examples

Feature Addition

git commit -m "✨ feat(auth): add OAuth2 login support

- Implemented Google OAuth2 provider
- Added token refresh mechanism
- Updated user session handling

Closes #123"

Bug Fix

git commit -m "🐛 fix(api): handle null response in user endpoint

The API was crashing when user data was incomplete.
Added null checks and default values.

Fixes #456"

Documentation

git commit -m "📝 docs: update API documentation for v2 endpoints"

Refactoring

git commit -m "♻️ refactor(utils): extract validation logic to separate module"

Fast Commit Workflow

For quick commits when the change is clear-cut:

1. Stage all changes: git add .
2. Generate 3 commit message suggestions
3. Auto-select the first one

This works well when you're confident the change is straightforward.

Pre-commit Checks

Run these before committing:

• Linting (ESLint, Prettier)
• Type checking (TypeScript)
• Unit tests

You can use husky to set up pre-commit hooks that run these checks automatically.

Next Steps

Check out Five Whys Analysis for root cause debugging.