Selects and applies gitmoji emoji prefixes for Git commit messages, integrated with Conventional Commits format. Use when the user asks about gitmoji, wants an emoji for a commit message, asks 'which emoji for...', 'quel emoji pour...', mentions commit emoji conventions, says 'prefix my commit', 'gitmoji for', 'emoji commit', or wants to decorate commit messages with standardized emoji. DO NOT USE when: the user wants plain Conventional Commits with no emoji; general Git help → use git-hero-git-guru.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Selects and applies gitmoji emoji prefixes for Git commit messages, integrated with Conventional Commits format. Use when the user asks about gitmoji, wants an emoji for a commit message, asks 'which emoji for...', 'quel emoji pour...', mentions commit emoji conventions, says 'prefix my commit', 'gitmoji for', 'emoji commit', or wants to decorate commit messages with standardized emoji. DO NOT USE when: the user wants plain Conventional Commits with no emoji; general Git help → use git-hero-git-guru.
user-invocable
false
Gitmoji
Standardized emoji guide for commit messages. Reference: gitmoji.dev
Conventional Commits Integration
Gitmoji prefixes the Conventional Commits format — the CC structure stays intact:
<emoji> <type>(<scope>): <description>
Examples:
Change
Commit message
Add Google OAuth login
✨ feat(auth): add OAuth2 login with Google
Fix cart double-submit
🐛 fix(cart): prevent double-submission on slow networks
Upgrade React to v19
⬆️ chore(deps): upgrade React to v19
CC Type → Default Gitmoji
CC Type
Emoji
Code
feat
✨
:sparkles:
fix
🐛
:bug:
docs
📝
:memo:
style
🎨
:art:
refactor
♻️
:recycle:
perf
⚡️
:zap:
test
✅
:white_check_mark:
chore
🔧
:wrench:
ci
💚
:green_heart:
build
👷
:construction_worker:
revert
⏪️
:rewind:
Use the default when no more specific gitmoji applies. Override with a more precise emoji when the context warrants it (see below).
Selection Guide — Overriding Defaults
Fix variants
Situation
Emoji
Code
Regular bug fix
🐛
:bug:
Critical production hotfix
🚑️
:ambulance:
Simple non-critical fix
🩹
:adhesive_bandage:
Security or privacy fix
🔒️
:lock:
Typo fix
✏️
:pencil2:
Compiler / linter warning fix
🚨
:rotating_light:
Feat variants
Situation
Emoji
Code
New feature (default)
✨
:sparkles:
New project / initial commit
🎉
:tada:
UI / style changes
💄
:lipstick:
Animations / transitions
💫
:dizzy:
Business logic
👔
:necktie:
Chore variants
Situation
Emoji
Code
Configuration files
🔧
:wrench:
Dev scripts
🔨
:hammer:
Add dependency
➕
:heavy_plus_sign:
Remove dependency
➖
:heavy_minus_sign:
Upgrade dependency
⬆️
:arrow_up:
Downgrade dependency
⬇️
:arrow_down:
Pin dependency
📌
:pushpin:
.gitignore
🙈
:see_no_evil:
Removal variants
Situation
Emoji
Code
Remove code or files
🔥
:fire:
Remove dead code specifically
⚰️
:coffin:
Deprecate (mark for future cleanup)
🗑️
:wastebasket:
Common Confusions
:art: vs :recycle: — :art: is cosmetic (formatting, structure). :recycle: is behavioral (logic refactoring).
:fire: vs :coffin: — :fire: removes any code/files. :coffin: specifically targets dead/unreachable code.
:wrench: vs :hammer: — :wrench: is config files (tsconfig, eslint). :hammer: is dev scripts (Makefile, build scripts).
:white_check_mark: vs :test_tube: — :white_check_mark: for passing tests. :test_tube: for intentionally failing tests (TDD red phase).
:sparkles: vs :heavy_plus_sign: — :sparkles: adds a feature. :heavy_plus_sign: adds a dependency.
PASS. The load-bearing lift is the override / Common-Confusions tables. On gitmoji-002 every baseline picked generic 🔥 :fire: for dead-code removal (should be ⚰️ :coffin:) and haiku also missed ➕ for a new dependency; the skill fixes both — haiku 67→100 (+33). gitmoji-001 (security override + no-emoji opt-out) was at ceiling (all models 100% with and without — no regression; the opt-out is honoured unaided), so value lives in the subtle picks. Gate per skill-optimizer/release-gates.md.
