comparison

git-agent vs Commitizen

Commitizen is a CLI tool that guides developers through commit message creation with interactive prompts following the Conventional Commits specification.

Featuregit-agentCommitizen
Atomic commit splittinggit-agentYesCommitizenNo
Conventional Commits formatgit-agentYesCommitizenYes
LLM-backed message draftinggit-agentYesCommitizenno — prompt-based
Pre-commit hook integration with retry loopgit-agentYesCommitizenpartial — hook install only
Dry-run preview before committinggit-agentYesCommitizenNo
Amend last commit messagegit-agentYesCommitizenyes — cz amend
Free shared gatewaygit-agentYesCommitizenyes — no LLM, prompt only
Config-file based scope definitionsgit-agentyes — .git-agent/config.ymlCommitizenyes — .cz.toml
git-agent
brew install gitagenthq/tap/git-agent
Commitizen
pip install commitizen # or npm install -g commitizen
git-agent
fix(api): handle missing Content-Type header on multipart uploads - return 415 Unsupported Media Type when Content-Type is absent instead of 500 - add boundary extraction helper to avoid duplicate parsing logic - cover the missing-header case with a dedicated test Clients sending multipart data without an explicit Content-Type caused an unhandled exception; the explicit check converts that to a client error.
Commitizen
fix(api): handle missing Content-Type header Resolves multipart upload 500 error.
Is Commitizen better for teams that prefer manual control?
Commitizen prompts you to fill in each field manually, which gives full control but adds friction per commit. git-agent drafts the message automatically and lets you edit before confirming.
Does git-agent require a Python or Node.js runtime like Commitizen?
No. git-agent is a single Go binary. It has no runtime dependencies beyond git itself.
Can I migrate from Commitizen to git-agent without losing my commit history?
Migration requires no changes to git history. Run git-agent init to generate .git-agent/config.yml with your scopes and uninstall the Commitizen hook.