Gitmoji Cheatsheet 🔒 Runs locally in your browser — nothing is uploaded.

Search, filter, and copy commit-ready gitmoji codes.

About this tool

Gitmoji is a community convention — not a Git feature — for prefixing commit messages with an emoji that signals their intent at a glance: ✨ for a new feature, 🐛 for a bug fix, 📝 for documentation, ♻️ for a refactor, and around 70 more covering everything from CI changes to accessibility improvements. Skimming a `git log` full of gitmoji-prefixed messages lets you spot what kind of work happened without reading every line, and some teams tie the emoji directly to changelog generation or semver bumps.

This cheatsheet lists every emoji from the official gitmoji data set with its `:code:` shortcode, description, and a rough category, and lets you search or filter by category to find the right one fast. Each row has three copy buttons: the emoji itself, the `:code:` shortcode with a trailing space ready to paste, or a full `git commit -m ":code: "` line you can paste straight into a terminal and finish typing. Everything runs locally in your browser — nothing you type is sent anywhere.

This is an independent reference built on the open-source gitmoji data from carloscuesta/gitmoji (MIT licensed). It is not affiliated with or endorsed by the original project — for the canonical list and official tooling (including a CLI and IDE extensions), see gitmoji.dev.

Frequently asked questions

What is gitmoji?

Gitmoji is a community convention that prefixes Git commit messages with an emoji to signal, at a glance, what kind of change the commit makes — ✨ for a new feature, 🐛 for a bug fix, 📝 for documentation, and so on. It isn't a Git feature or a required standard; it's just a naming convention some teams and open-source projects adopt to make commit history easier to skim, and in some workflows to drive changelog generation or automatic semver bumps.

How do I use gitmoji in my commit messages?

Find the gitmoji that matches what you changed, then put its emoji (or its :code: shortcode, if your git host or terminal renders shortcodes like GitHub comments do) at the very start of your commit message, followed by a short description — for example `✨ Add dark mode toggle` or `:bug: Fix off-by-one error in pagination`. This tool's "Commit" copy button builds the full `git commit -m ":code: "` command for you, so you can paste it straight into your terminal and just type the rest of the message.

Is this an official gitmoji tool?

No — this is an independent reference built on top of the open-source gitmoji data published by Carlos Cuesta at github.com/carloscuesta/gitmoji (MIT licensed). It isn't affiliated with, endorsed by, or officially connected to that project in any way; it exists purely to make searching and copying the existing gitmoji list faster. For the canonical list, the official CLI, and IDE integrations, visit gitmoji.dev.

What does the small 'major/minor/patch' label next to some gitmoji mean?

That's the semantic-versioning (semver) bump the gitmoji project suggests a commit of that type implies, if your project follows semver and automates version bumps from commit history — for example 💥 (boom) suggests a major bump because it signals a breaking change, and ✨ (sparkles) suggests minor because it adds a feature without breaking anything. Many gitmoji, like 📝 (memo) for documentation, carry no semver implication at all and are left blank. Treat it as a helpful hint, not a rule your commit is forced to follow — plenty of teams use gitmoji purely for readability, with no versioning automation attached.