comparison

git-agent vs gitmoji-cli

gitmoji-cli is an interactive commit tool that standardises commit messages using emoji prefixes from the Gitmoji specification.

Featuregit-agentgitmoji-cli
Atomic commit splittinggit-agentYesgitmoji-cliNo
Conventional Commits formatgit-agentYesgitmoji-clipartial — Gitmoji format
LLM-backed message draftinggit-agentYesgitmoji-clino — manual selection
Pre-commit hook integration with retry loopgit-agentYesgitmoji-cliNo
Dry-run preview before committinggit-agentYesgitmoji-cliNo
Amend last commit messagegit-agentYesgitmoji-cliNo
Free shared gatewaygit-agentYesgitmoji-cliyes — no LLM
Config-file based setupgit-agentyes — .git-agent/config.ymlgitmoji-climinimal
git-agent
brew install gitagenthq/tap/git-agent
gitmoji-cli
npm install -g gitmoji-cli
git-agent
docs(api): add OpenAPI 3.1 schema for /orders endpoint - document all request parameters and their validation constraints - add 200, 400, 401, and 404 response schemas with example payloads - note rate limit headers in the response description The endpoint was undocumented; client teams were inferring the schema from integration tests rather than a canonical source.
gitmoji-cli
:memo: add OpenAPI schema for orders endpoint
Is Gitmoji compatible with Conventional Commits tooling?
Gitmoji uses emoji prefixes instead of type keywords. Most changelog generators and semantic release tools expect the Conventional Commits type keyword format and do not parse Gitmoji prefixes.
Can I use git-agent if my team currently uses gitmoji-cli?
Yes. Run git-agent init and update your team's contribution guidelines to use the Conventional Commits type keywords instead of emoji. Existing commit history is unaffected.
Does git-agent work alongside a Gitmoji commit-msg hook?
git-agent installs its own pre-commit hook for message validation. Using it alongside a Gitmoji hook that enforces a different format would cause hook failures. The two tools are designed for different commit conventions.