Agent skill · writing content · github
gitmoji
Generates commit messages following the gitmoji convention (https://gitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to "write a gitmoji commit", "add an emoji to my commit message", "which gitmoji should I use", "gitmoji this change", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.
Why this skill is useful
Codifies the gitmoji commit message format, which the AI could infer but now doesn't have to guess.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Gitmoji Generates commit messages that follow the gitmoji convention: every commit starts with an emoji that identifies the intent of the change at a glance. Given a diff, a list of staged files, or a plain description of a change, this skill picks the single most appropriate gitmoji and writes a concise, well-formed commit message around it. This skill only generates the message — it never runs git commit or any other git command. The output is a copyable message for the user to use. When to Use This Skill User says "write a gitmoji commit", "gitmoji this change", or "add an emoji to my commit message" User asks "which gitmoji should I use for this?" User pastes a git diff or describes a change in a project that uses gitmoji-style commit history User wants an expressive, scannable commit history using emojis When not to use: if the project follows plain Conventional Commits (feat:, fix:, ...) without emojis, use the conventional-commit or commit-message-storyteller skill instead. If unsure which convention the project uses, ask the user to provide recent commit history (for example, the output of git log --oneline -10). Message Format The gitmoji specification: intention — exactly one gitmoji expressing the goal of the commit scope (optional) — the section of the codebase affected, in parentheses message — a brief imperative explanation of the change Examples: Emoji Style: Unicode vs Shortcode Gitmoji supports two equivalent notations: Style Example When to prefer ------- --------- ---------------- Unicode ✨ add dark mode Default — renders everywhere, shorter subject line Shortcode :sparkles: add dark mode Platforms that render shortcodes (GitHub, GitLab) or teams that grep commit logs by code Match the repository's existing history. If recent commits use :sparkles:-style shortcodes, generate shortcodes; otherwise default to unicode emojis. How It Works Step 1: Understand the Change Work from whatever the user provides: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gitmoji