git-commit-style-gitmoji

Write Git commit messages with one Gitmoji representing the primary intent.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill git-commit-style-gitmoji-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-style-gitmoji
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/git-commit-style-gitmoji
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill git-commit-style-gitmoji-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing consistent, meaningful commit messages is hard when teams mix styles or pick emojis arbitrarily. This Skill enforces a single-emoji Gitmoji convention so every commit clearly communicates its primary intent. ## Core Features & Use Cases - Intent-based emoji selection: Inspects the staged diff and picks exactly one Gitmoji matching the change's primary purpose, backed by a full reference table of 70+ official Gitmojis. - Structured message format: Produces messages in the <emoji> [(scope)]: <imperative summary> shape with optional scope and body. - Safety guardrails: Prevents claiming unverified tests or fixes, leaking secrets or private paths, and committing or pushing without explicit request. - Use Case: After staging a bug fix, ask for a commit message and receive something like 🐛 bootstrap: preserve existing context files that follows the repository's established Gitmoji style. ## Quick Start Ask the assistant to write a Gitmoji-style commit message for the currently staged changes.

Frequently Asked Questions about git-commit-style-gitmoji

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

FAQPage Schema
How do I write a Gitmoji commit message?

Inspect the staged diff, choose one emoji matching the primary intent, then write an imperative summary in the format `<emoji> [(scope)]: <summary>`. Add a body only when the reason, migration, or verification context would otherwise be lost.

Which Gitmoji should I use for a bug fix or new feature?

Use 🐛 for bug fixes and ✨ for new features. The references/gitmojis.json file lists over 70 official Gitmojis with descriptions, so select the entry whose intent matches the change rather than choosing by appearance.

Can I use multiple emojis in one commit message?

No. The convention requires exactly one emoji representing the primary intent. Stacking several emojis to summarize unrelated changes is discouraged; keep one coherent outcome per commit instead.

When should I not use Gitmoji-style commits?

Follow the repository's existing commit rules first. Use Gitmoji only when the user or project explicitly requests it or the style is already established; otherwise default to the project's conventional format.

Does this Skill commit or push changes automatically?

No. It only drafts the commit message. It will not amend, commit, or push merely because a message was requested, and it avoids including secrets, private paths, or non-public issue references.