38 lines
1.4 KiB
Plaintext
38 lines
1.4 KiB
Plaintext
Analyze the following git diff and generate a concise, descriptive commit message following the Conventional Commits format.
|
|
|
|
## Requirements:
|
|
1. Format: `<type>(<scope>): <description>`
|
|
2. Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
|
|
3. Keep the description concise (50 chars or less for first line)
|
|
4. Use imperative mood ("add" not "added")
|
|
5. Don't capitalize the first letter of description
|
|
6. No period at the end of description
|
|
|
|
## Change Type Detection:
|
|
- **feat**: New feature, enhancement, or user-facing change
|
|
- **fix**: Bug fix, error correction, patch
|
|
- **docs**: Documentation only changes
|
|
- **style**: Formatting, missing semicolons, etc. (no code change)
|
|
- **refactor**: Code change that neither fixes bug nor adds feature
|
|
- **perf**: Performance improvement
|
|
- **test**: Adding/missing tests, refactoring tests
|
|
- **build**: Build system, CI, dependencies
|
|
- **ci**: CI configuration changes
|
|
- **chore**: Maintenance tasks, cleanup, tooling changes
|
|
- **revert**: Reverting a previous commit
|
|
|
|
## Scope Detection:
|
|
- Detect the main area/module affected
|
|
- Common scopes: api, auth, db, ui, utils, core, config
|
|
- Use the directory name or primary file category
|
|
- Omit scope if changes span multiple areas
|
|
|
|
## Output Format:
|
|
Return ONLY the commit message (no explanation, no quotes):
|
|
|
|
```
|
|
<type>(<scope>): <description>
|
|
```
|
|
|
|
If multiple changes are present, provide a single summary commit message that captures the overall change.
|