finds.dev← search

// the find

ahmadawais/Emoji-Log

★ 903 · JavaScript · MIT · updated Sep 2025

Emoji-Log — An Emoji Git commit log messages spec. [ 📦👌🐛📖🚀🤖 ‼️]

Emoji-Log is a personal git commit message convention: seven emoji prefixes (NEW, IMPROVE, FIX, DOC, RELEASE, TEST, BREAKING) meant to make `git log` scannable at a glance. It ships as a spec plus a pile of tooling — shell functions, git aliases, a VSCode extension, Alfred/Raycast snippets, and a commitlint config — for solo devs or small teams who want something lighter than full Conventional Commits.

The category list is genuinely small (seven, one of them edge-case 'breaking'), which is the actual selling point over something like gitmoji's sprawling emoji table — small enough to memorize and stick with. It backs the spec with real tooling instead of just a markdown file: bash/zsh/fish functions, git aliases, and a separate commitlint-config-emoji-log package for anyone who wants to enforce it. The gcap-style helpers (add+commit+push in one call) match how a lot of solo-repo workflows actually happen day to day.

Nothing in the repo actually enforces the format — the commitlint package exists but isn't wired into a pre-commit hook here, so adoption is on the honor system unless you do that integration yourself. `gcap` runs `git add . && git commit && git push` by default, which is a rough default to copy-paste into a `.bashrc` since it has no concept of staged vs. unstaged changes or branch protection. There's no mapping to changelog/release automation (no semantic-release, no changesets), so the RELEASE/BREAKING categories are purely cosmetic rather than feeding any tooling. The repo itself has no tests or CI despite shipping a commitlint config package that other projects would depend on.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →