Gitmoji
Generate a copyable commit message in the https://gitmoji.dev/ convention: infer the dominant change intent, select exactly one gitmoji, match unicode versus shortcode style, and write an imperative subject plus optional body.
When to invoke
- "Write a gitmoji commit for these changes."
- "Gitmoji this diff."
- "Which gitmoji should I use?"
- "Add an emoji to my commit message."
- "This project uses gitmoji-style commits."
Message format
<intention> [scope?][:?] <message>
| Field |
Rule |
intention |
Exactly one gitmoji expressing the goal of the commit. |
scope |
Optional codebase area in parentheses; use only if the existing history uses scopes or it clarifies the change. |
message |
Brief imperative phrase, lowercase start, no trailing period. |
| body |
Optional; include only when the why is not obvious from the subject or when documenting a breaking change. |
Examples:
✨ add multi-tenant support to the billing service
🐛 (auth) prevent token refresh loop on expired sessions
♻️ (api): extract pagination logic into shared helper
Emoji selection
Consult references/gitmoji-reference.md before final selection because the full official list has 75 gitmojis and a more specific choice may exist.
| Emoji |
Shortcode |
Use when |
| ✨ |
:sparkles: |
Introduce features. |
| 🐛 |
:bug: |
Fix a bug. |
| 🚑️ |
:ambulance: |
Critical production hotfix. |
| 📝 |
:memo: |
Add or update documentation. |
| ♻️ |
:recycle: |
Refactor without behavior change. |
| ✅ |
:white_check_mark: |
Add, update, or pass tests. |
| ⚡️ |
:zap: |
Improve performance. |
| 🎨 |
:art: |
Improve structure or formatting of code. |
| 🔥 |
:fire: |
Remove code or files. |
| 🔒️ |
:lock: |
Fix security or privacy issues. |
| ⬆️ |
:arrow_up: |
Upgrade dependencies. |
| 🔧 |
:wrench: |
Add or update configuration files. |
| 💄 |
:lipstick: |
Add or update UI/style files. |
| 💥 |
:boom: |
Introduce breaking changes. |
| 🚨 |
:rotating_light: |
Fix compiler or linter warnings. |
| 🌐 |
:globe_with_meridians: |
Internationalization or localization. |
Procedure
- Work from the provided diff, staged files, modified paths, or plain description.
- If the repository style is unknown and history is available, inspect
git log --oneline -10 to choose unicode versus shortcode and scope style.
- Identify the dominant intent. If the change mixes unrelated feature, fix, refactor, test, and docs work, choose the dominant intent and suggest splitting commits.
- Prefer specific emojis over generic ones: typo ✏️ instead of 🐛, file move 🚚 instead of ♻️, trivial fix 🩹 instead of 🐛, security 🔒️ over bug.
- Write a subject under 72 characters including the emoji when possible.
- Add a body only for rationale, breaking changes, or context that does not fit the subject.
- Output the message in a code block and one short explanation. Do not execute
git commit.
Style decisions
| Situation |
Rule |
| Unicode history |
Default to unicode, e.g. ✨ add dark mode. |
| Shortcode history |
Match shortcode, e.g. :sparkles: add dark mode. |
| Tests |
Use ✅ for passing tests; use 🧪 only for intentionally failing tests such as a TDD red step. |
| Hotfix |
Use 🚑️ only for urgent production fixes; ordinary bugs are 🐛. |
| Formatting |
Use 🎨 for code structure/formatting; use 💄 for visual UI/style files. |
| Breaking change |
Use 💥 and document the break in the body. |
| Revert |
Use ⏪️ with a subject referencing the reverted commit. |
| Merge |
Use 🔀 merge branch '<name>' into <target>. |
| Initial commit |
Use 🎉 begin project. |
| Work in progress |
Use 🚧 and say what remains. |
| No obvious match |
Re-scan references/gitmoji-reference.md, then fall back to ✨, 🐛, or ♻️. |
Limits
- Do not run
git commit or any other mutating git command.
- If the project follows plain Conventional Commits from https://www.conventionalcommits.org/ without emojis, use the
git-commit skill instead.
- If the convention is ambiguous, ask for recent history or inspect
git log --oneline -10 when allowed.
Progressive disclosure and bundled resources
references/gitmoji-reference.md: complete official gitmoji list; read it before choosing a final emoji.
Compatibility terminology
Preserve these baseline terms when they appear in user input, existing files, logs, or migration output; they are included to keep legacy wording, commands, paths, and API names recognizable during execution.
adding/updatingcommit-message-storytellerfeat:fix:non-criticalre-triggeredstaged/modifiedwell-formed
Shortcode style may be preferred on GitHub or GitLab when repository history uses codes such as :sparkles:.
Output template
## Gitmoji commit message
```text
<emoji or shortcode> (<optional-scope>) <imperative subject>
<optional body>
Why:
Style matched: unicode | shortcode | unknown
## Quality gate
- [ ] Exactly one gitmoji or shortcode starts the subject.
- [ ] The selected emoji matches the dominant intent and was checked against `references/gitmoji-reference.md`.
- [ ] Unicode versus shortcode style matches existing history when evidence is available.
- [ ] Subject is imperative, concise, lowercase after the emoji unless a proper noun requires capitalization, and has no trailing period.
- [ ] Mixed unrelated changes are called out as candidates for separate commits.
- [ ] No git command that mutates history is executed.
## References
- [gitmoji](https://gitmoji.dev)
- [gitmoji with trailing slash](https://gitmoji.dev/)
- [Conventional Commits](https://www.conventionalcommits.org/)
1---2name: gitmoji-23description: Generate commit messages that follow the gitmoji convention (https://gitmoji.dev) by choosing the single best emoji or shortcode for a diff, staged change, or plain-language change description. Use when asked to write a gitmoji commit, add an emoji to a commit message, choose a gitmoji, gitmoji this change, or follow a gitmoji-style commit history. Generates the message only and does not run git commands.4license: MIT5---67# Gitmoji89Generate a copyable commit message in the https://gitmoji.dev/ convention: infer the dominant change intent, select exactly one gitmoji, match unicode versus shortcode style, and write an imperative subject plus optional body.1011## When to invoke1213- "Write a gitmoji commit for these changes."14- "Gitmoji this diff."15- "Which gitmoji should I use?"16- "Add an emoji to my commit message."17- "This project uses gitmoji-style commits."1819## Message format2021```text22<intention> [scope?][:?] <message>23```2425| Field | Rule |26| --- | --- |27| `intention` | Exactly one gitmoji expressing the goal of the commit. |28| `scope` | Optional codebase area in parentheses; use only if the existing history uses scopes or it clarifies the change. |29| `message` | Brief imperative phrase, lowercase start, no trailing period. |30| body | Optional; include only when the why is not obvious from the subject or when documenting a breaking change. |3132Examples:3334```text35✨ add multi-tenant support to the billing service36🐛 (auth) prevent token refresh loop on expired sessions37♻️ (api): extract pagination logic into shared helper38```3940## Emoji selection4142Consult `references/gitmoji-reference.md` before final selection because the full official list has 75 gitmojis and a more specific choice may exist.4344| Emoji | Shortcode | Use when |45| --- | --- | --- |46| ✨ | `:sparkles:` | Introduce features. |47| 🐛 | `:bug:` | Fix a bug. |48| 🚑️ | `:ambulance:` | Critical production hotfix. |49| 📝 | `:memo:` | Add or update documentation. |50| ♻️ | `:recycle:` | Refactor without behavior change. |51| ✅ | `:white_check_mark:` | Add, update, or pass tests. |52| ⚡️ | `:zap:` | Improve performance. |53| 🎨 | `:art:` | Improve structure or formatting of code. |54| 🔥 | `:fire:` | Remove code or files. |55| 🔒️ | `:lock:` | Fix security or privacy issues. |56| ⬆️ | `:arrow_up:` | Upgrade dependencies. |57| 🔧 | `:wrench:` | Add or update configuration files. |58| 💄 | `:lipstick:` | Add or update UI/style files. |59| 💥 | `:boom:` | Introduce breaking changes. |60| 🚨 | `:rotating_light:` | Fix compiler or linter warnings. |61| 🌐 | `:globe_with_meridians:` | Internationalization or localization. |6263## Procedure64651. Work from the provided diff, staged files, modified paths, or plain description.662. If the repository style is unknown and history is available, inspect `git log --oneline -10` to choose unicode versus shortcode and scope style.673. Identify the dominant intent. If the change mixes unrelated feature, fix, refactor, test, and docs work, choose the dominant intent and suggest splitting commits.684. Prefer specific emojis over generic ones: typo ✏️ instead of 🐛, file move 🚚 instead of ♻️, trivial fix 🩹 instead of 🐛, security 🔒️ over bug.695. Write a subject under 72 characters including the emoji when possible.706. Add a body only for rationale, breaking changes, or context that does not fit the subject.717. Output the message in a code block and one short explanation. Do not execute `git commit`.7273## Style decisions7475| Situation | Rule |76| --- | --- |77| Unicode history | Default to unicode, e.g. `✨ add dark mode`. |78| Shortcode history | Match shortcode, e.g. `:sparkles: add dark mode`. |79| Tests | Use ✅ for passing tests; use 🧪 only for intentionally failing tests such as a TDD red step. |80| Hotfix | Use 🚑️ only for urgent production fixes; ordinary bugs are 🐛. |81| Formatting | Use 🎨 for code structure/formatting; use 💄 for visual UI/style files. |82| Breaking change | Use 💥 and document the break in the body. |83| Revert | Use ⏪️ with a subject referencing the reverted commit. |84| Merge | Use 🔀 `merge branch '<name>' into <target>`. |85| Initial commit | Use 🎉 `begin project`. |86| Work in progress | Use 🚧 and say what remains. |87| No obvious match | Re-scan `references/gitmoji-reference.md`, then fall back to ✨, 🐛, or ♻️. |8889## Limits9091- Do not run `git commit` or any other mutating git command.92- If the project follows plain Conventional Commits from https://www.conventionalcommits.org/ without emojis, use the `git-commit` skill instead.93- If the convention is ambiguous, ask for recent history or inspect `git log --oneline -10` when allowed.9495## Progressive disclosure and bundled resources9697- `references/gitmoji-reference.md`: complete official gitmoji list; read it before choosing a final emoji.9899## Compatibility terminology100101Preserve these baseline terms when they appear in user input, existing files, logs, or migration output; they are included to keep legacy wording, commands, paths, and API names recognizable during execution.102103- `adding/updating`104- `commit-message-storyteller`105- `feat:`106- `fix:`107- `non-critical`108- `re-triggered`109- `staged/modified`110- `well-formed`111112Shortcode style may be preferred on GitHub or GitLab when repository history uses codes such as `:sparkles:`.113114## Output template115116```markdown117## Gitmoji commit message118119```text120<emoji or shortcode> (<optional-scope>) <imperative subject>121122<optional body>123```124125**Why:** <one sentence explaining why this gitmoji matches the dominant intent>126**Style matched:** unicode | shortcode | unknown127```128129## Quality gate130131- [ ] Exactly one gitmoji or shortcode starts the subject.132- [ ] The selected emoji matches the dominant intent and was checked against `references/gitmoji-reference.md`.133- [ ] Unicode versus shortcode style matches existing history when evidence is available.134- [ ] Subject is imperative, concise, lowercase after the emoji unless a proper noun requires capitalization, and has no trailing period.135- [ ] Mixed unrelated changes are called out as candidates for separate commits.136- [ ] No git command that mutates history is executed.137138## References139140- [gitmoji](https://gitmoji.dev)141- [gitmoji with trailing slash](https://gitmoji.dev/)142- [Conventional Commits](https://www.conventionalcommits.org/)
paulasilvatech