Skip to content

Instantly share code, notes, and snippets.

@shuantsu
Last active November 17, 2025 13:27
Show Gist options
  • Select an option

  • Save shuantsu/f8a081f1451798c3c2188c5ec6d836c0 to your computer and use it in GitHub Desktop.

Select an option

Save shuantsu/f8a081f1451798c3c2188c5ec6d836c0 to your computer and use it in GitHub Desktop.
Git Commit Message Generator
Create a semantic commit message in English following these guidelines:
- Use git diff HEAD to analyze the changes
- Format: emoji + type + colon + space + description
- Types: feat, fix, docs, refactor, style, perf, config, remove
- Emojis: ✨ feat, πŸ› fix, πŸ“ docs, ♻️ refactor, 🎨 style, ⚑ perf, πŸ”§ config, πŸ—‘οΈ remove
- First line: max 72 chars
- If needed, add blank line then bullet list with details (use "- " prefix)
- Use present tense ("add" not "added")
- Be specific about what changed and why
- Only use emoji on the first line
Example:
✨ feat: add map style persistence with localStorage
- Create utility to save/load map preferences across sessions
- Add compact style selector with flyout menu to fence modal
- Preserve polygon data when switching between map styles
- Implement click-outside handler to close style menu
@shuantsu
Copy link
Author

shuantsu commented Nov 17, 2025

If the tool has tools to access the terminal, it uses git diff HEAD to see the changes.

If the tool is a chatbot without access, you must provide the git diff log yourself for the changes to be analyzed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment