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.
Profile →npx skills add github/awesome-copilot --skill gitmoji --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Gitmoji Generates commit messages that follow the [gitmoji](https://gitmoji.dev/) 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](https://www.conventionalcommits.org/) (`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
- When to Use This Skill
- Message Format
- Emoji Style: Unicode vs Shortcode
- How It Works
- Step 1: Understand the Change
- Step 2: Identify the Dominant Intent
- Step 3: Pick Exactly One Emoji
- Step 4: Write the Message
- Step 5: Output
- Edge Cases
- Quick Reference
Get your staged diff to paste into Copilot git diff --staged Check which emoji style the repo already uses git log --oneline -10
What does the gitmoji skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gitmoji --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.