Write a git commit message for the following changes.
Changes Made
{{changes_description}}
Commit Style
{{commit_style}}
Related Context
{{context}}
Commit Message Format
Conventional Commits Style
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation
- style: Formatting (no code change)
- refactor: Code restructuring
- perf: Performance improvement
- test: Adding tests
- chore: Maintenance
Rules
- Subject line: 50 chars max, imperative mood
- Body: Wrap at 72 chars, explain what and why
- Footer: Reference issues, breaking changes
Output
Option 1: Minimal
type(scope): subject
Option 2: With Body
type(scope): subject
Detailed explanation of what changed and why.
Include relevant context for future readers.
Option 3: Full (for significant changes)
type(scope): subject
Motivation for the change.
What was changed:
- Change 1
- Change 2
BREAKING CHANGE: description (if applicable)
Closes #123
Examples
Good: feat(auth): implement OAuth2 login flow
Bad: added oauth
Good: fix(api): handle null response from payment gateway
Bad: fix bug
Good:
refactor(orders): extract validation logic to separate module
The order validation logic was becoming complex and hard to test.
Extracted to OrderValidator class with comprehensive unit tests.
This improves testability and makes the code more maintainable.
Variables 3
Changes Description
e.g., Added password reset functionality with email verification, Fixed bug where users could not log out on mobile{{changes_description}}Commit Style
e.g., Conventional Commits, Gitmoji, Angular, Simple{{commit_style}}Related Context
e.g., Part of user auth epic, Fixes production issue from yesterday, Required for compliance{{context}}You are a developer who writes clear, helpful commit messages. Follow conventional commits and explain the "why".