How do I install the Devmoji skill?

Run npx skillmds@latest add lukevella/devmoji in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Devmoji safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Devmoji?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Devmoji free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Devmoji?

lukevella (@lukevella) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Devmoji by lukevella — Agent Skill

Name: Devmoji
Author: lukevella

Devmoji

Devmoji commit message emoji conventions. Use when writing git commit messages, formatting commit descriptions, or choosing the right emoji prefix for a commit. Triggers on "commit message", "git commit", "commit emoji", "devmoji".

lukevella 59bd593 2.5 KB Updated Sep 17, 2026

File contents

Devmoji Commit Conventions

This project uses emoji prefixes in commit messages following devmoji/gitmoji conventions. Every commit message MUST start with an emoji followed by a space, then the description.

Format

<emoji> <Short description>

Examples from this repo:

🐛 Fix hydration error on dashboard page
✨ Add support for in-memory rate limiting
♻️ Move locale sync
⚡️ Preload dayjs locales
💄 Disable overscroll

Emoji Reference

Emoji	Code	When to use
✨	`:sparkles:`	New feature or capability
🐛	`:bug:`	Bug fix
♻️	`:recycle:`	Refactoring (no feature or fix)
⚡️	`:zap:`	Performance improvement
💄	`:lipstick:`	UI/style/cosmetic change
🔧	`:wrench:`	Configuration file change
🔥	`:fire:`	Remove code or files
📝	`:memo:`	Documentation
🌐	`:globe_with_meridians:`	Internationalization/localization
🔒️	`:lock:`	Security fix or improvement
⬆️	`:arrow_up:`	Upgrade dependencies
🚀	`:rocket:`	Deploy or release
🔖	`:bookmark:`	Version tag / release
👷	`:construction_worker:`	CI/CD changes
🧑‍💻	`:technologist:`	Developer experience improvement
🌱	`:seedling:`	Seed data / database seeding
🔊	`:loud_sound:`	Add or update logs
➕	`:heavy_plus_sign:`	Add dependency
➖	`:heavy_minus_sign:`	Remove dependency
🚨	`:rotating_light:`	Fix linting / compiler warnings
✅	`:white_check_mark:`	Add or update tests
🏗️	`:building_construction:`	Architectural change
📦	`:package:`	Build system change
🗃️	`:card_file_box:`	Database / migration change
🩹	`:adhesive_bandage:`	Simple fix for non-critical issue
⏪️	`:rewind:`	Revert changes

Rules

Always prefix the commit message with exactly one primary emoji
No conventional commit type prefix — use 🐛 Fix bug not fix: 🐛 Fix bug
Capitalize the first word after the emoji
No period at the end of the subject line
Keep it short — subject line under 72 characters
Pick the most specific emoji that applies (e.g. 💄 for a pure CSS change, not ✨)

---name: devmojidescription: Devmoji commit message emoji conventions. Use when writing git commit messages, formatting commit descriptions, or choosing the right emoji prefix for a commit. Triggers on "commit message", "git commit", "commit emoji", "devmoji".---# Devmoji Commit ConventionsThis project uses emoji prefixes in commit messages following devmoji/gitmoji conventions. Every commit message MUST start with an emoji followed by a space, then the description.## Format```<emoji> <Short description>```**Examples from this repo:**- `🐛 Fix hydration error on dashboard page`- `✨ Add support for in-memory rate limiting`- `♻️ Move locale sync`- `⚡️ Preload dayjs locales`- `💄 Disable overscroll`## Emoji Reference| Emoji | Code | When to use ||-------|------|-------------|| ✨ | `:sparkles:` | New feature or capability || 🐛 | `:bug:` | Bug fix || ♻️ | `:recycle:` | Refactoring (no feature or fix) || ⚡️ | `:zap:` | Performance improvement || 💄 | `:lipstick:` | UI/style/cosmetic change || 🔧 | `:wrench:` | Configuration file change || 🔥 | `:fire:` | Remove code or files || 📝 | `:memo:` | Documentation || 🌐 | `:globe_with_meridians:` | Internationalization/localization || 🔒️ | `:lock:` | Security fix or improvement || ⬆️ | `:arrow_up:` | Upgrade dependencies || 🚀 | `:rocket:` | Deploy or release || 🔖 | `:bookmark:` | Version tag / release || 👷 | `:construction_worker:` | CI/CD changes || 🧑‍💻 | `:technologist:` | Developer experience improvement || 🌱 | `:seedling:` | Seed data / database seeding || 🔊 | `:loud_sound:` | Add or update logs || ➕ | `:heavy_plus_sign:` | Add dependency || ➖ | `:heavy_minus_sign:` | Remove dependency || 🚨 | `:rotating_light:` | Fix linting / compiler warnings || ✅ | `:white_check_mark:` | Add or update tests || 🏗️ | `:building_construction:` | Architectural change || 📦 | `:package:` | Build system change || 🗃️ | `:card_file_box:` | Database / migration change || 🩹 | `:adhesive_bandage:` | Simple fix for non-critical issue || ⏪️ | `:rewind:` | Revert changes |## Rules1. **Always prefix** the commit message with exactly one primary emoji2. **No conventional commit type prefix** — use `🐛 Fix bug` not `fix: 🐛 Fix bug`3. **Capitalize** the first word after the emoji4. **No period** at the end of the subject line5. **Keep it short** — subject line under 72 characters6. Pick the **most specific** emoji that applies (e.g. `💄` for a pure CSS change, not `✨`)

Frequently asked questions