Supply this file to the AI to generate a git commit message based on changes since the last commit. Messages use emoji bullet points for clarity and visual appeal.
The AI should:
- Analyze the git diff to understand changes
- Use the format:
type:\nfollowed by emoji bullet points - Each change gets its own line with an appropriate emoji
- Start with the commit type (feat, fix, refactor, docs, etc.) followed by a colon
- Add a newline, then list changes as emoji bullets
- Choose emojis that match the type of change
- Keep each bullet point concise and descriptive
- Prioritize the most impactful changes first
feat: New featuresfix: Bug fixesrefactor: Code refactoringdocs: Documentation changesstyle: Code style changestest: Test changeschore: Maintenance tasksperf: Performance improvementsci: CI/CD changesbuild: Build system changes
- 🔀 Routing, navigation, parallel/interception routes
- 🎯 Features, functionality
- 📝 Documentation, structure, updates
- 🔧 Configuration, setup
- ⚡ Performance, optimization
- 🐛 Bug fixes
- 🎨 UI, styling, components
- 📛 Badges, metadata
- 🔐 Auth, security
- 📦 Dependencies, packages
- ♻️ Refactoring, code quality
- 🗑️ Removal, deletion
- ✨ New functionality
docs:
📛 Added tech stack badges with package versions
📝 Updated project structure documentation
fix:
🐛 Resolved session type inference errors
🔧 Updated auth helper types
feat:
✨ Implemented password reset flow
📧 Added email verification with React Email
🔐 Created forgot-password action and form
refactor:
♻️ Converted all components to arrow functions
🎨 Migrated AlertDialog to Dialog component
🔀 Created shared auth content components
🎯 Preserved state on interception route refresh
📦 Updated dependencies
refactor:
♻️ Converted 35+ components from function declarations to arrow functions
🔀 Implemented interception routes for auth modals with state preservation
🎯 Created shared page content components (sign-in, sign-up, forgot-password)
🎨 Applied 16 canonical CSS class optimizations (data-disabled, data-inset, min-w-32)
🔧 Configured Biome useArrowFunction linter rule in complexity group
🗑️ Removed AlertDialog component in favor of Dialog
📦 Updated project dependencies (bun.lock, package.json)
- Run
git diffto see unstaged changes - Run
git diff --cachedto see staged changes - Run
git diff --statto see change summary - Analyze the changes and categorize them
- Count files changed and lines modified
- Generate a commit message:
- Start with commit type and colon (e.g.,
feat:,refactor:,docs:) - Add a newline
- List changes as emoji bullet points
- Each change on its own line
- Use relevant emojis from the common emojis list
- Order by importance (most impactful first)
- Keep bullet points concise and descriptive
- Start with commit type and colon (e.g.,
- Scale based on change size:
- Small (1-5 files): 2-3 bullet points
- Medium (6-15 files): 3-4 bullet points
- Large (16-30 files): 5-7 bullet points
- Extensive (30+ files): 7-10 bullet points