Gitmoji

Select the semantically appropriate gitmoji for a commit message.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/agent-core --skill gitmoji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Gitmoji
Source: https://github.com/ddaanet/agent-core/tree/main/skills/gitmoji
Command: npx skills add https://github.com/ddaanet/agent-core --skill gitmoji

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

This skill provides semantic mapping of commit messages to the correct gitmoji emoji, ensuring consistent and meaningful commit history.

Core Features & Use Cases

  • Semantic selection: Chooses the most appropriate gitmoji based on commit intent (fix, feature, docs, refactor, etc.).
  • Index-driven: Reads the gitmoji index and applies rules for precise matching.
  • Use Case: For a commit message like 'Fix login crash', the skill returns '🐛' as the prefix.

Quick Start

Use the Gitmoji skill to prefix a commit message with the correct emoji, e.g., '🐛 Fix login crash in auth flow'.

Frequently Asked Questions about Gitmoji

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically add semantic emoji to git commit messages?

To automatically add semantic emoji to git commit messages, this skill applies semantic matching against the official gitmoji index to return the correct single emoji prefix. It detects commit intent like bug fixes or features to prepend the appropriate character.

What is the best way to map a conventional commit message to a gitmoji?

The best way to map conventional commit messages to a gitmoji is using an index-driven matching approach. This skill reads the official gitmoji index and applies rules to select the most semantically appropriate emoji for intents like refactoring or documentation updates.

How does semantic emoji selection work for version control commits?

Semantic emoji selection for version control commits works by reading the gitmoji index and performing semantic matching on your commit message. It analyzes the text to identify typical commit intents and returns a single emoji character to prepend to the message.

Do I need curl and jq installed to use this gitmoji mapping skill?

Yes, you need curl and jq installed because this skill relies on scripts that use these dependencies to read and parse the official gitmoji index. They are required to execute the semantic matching process and return the correct emoji.

Can I use this skill to prefix documentation and refactor commits with the correct gitmoji?

Yes, you can use this skill to prefix documentation and refactor commits because it covers typical commit intents across software projects. It maps the specific semantic meaning of your message to the corresponding gitmoji from the index.

What are the limitations of using an index-driven approach for commit message emoji selection?

A limitation of index-driven commit message emoji selection is that matching is restricted to the predefined intents within the official gitmoji index. If a commit intent is highly unconventional, the skill may not return a perfectly matched emoji character.