comparisongit-agent vs convco
convco is a Rust-based CLI for enforcing Conventional Commits, generating changelogs, and bumping versions — it validates commits but does not generate messages.
feature comparison
Atomic commit splittinggit-agent✓
convco—
Conventional Commits formatgit-agent✓
convcoyes — linting focus
LLM-backed message draftinggit-agent✓
convco—
Pre-commit hook integration with retry loopgit-agent✓
convcoyes — linting only
Dry-run preview before committinggit-agent✓
convco—
Amend last commit messagegit-agent✓
convco—
Free tier with built-in credentialsgit-agent✓
convcoyes — no LLM
Changelog generationgit-agent—
convco✓
install
git-agentbrew install gitagenthq/tap/git-agent
convcobrew install convco # or cargo install convco
output example
git-agentchore(deps): upgrade OpenTelemetry SDK to 1.25.0
- bump otel-sdk, otel-exporter-otlp, and otel-instrumentation-http in lockstep
- update trace provider initialisation to new BatchSpanProcessor API
- remove deprecated SimpleSpanProcessor usage flagged in 1.24.0 release notes
The 1.24.x deprecation warnings were cluttering test output; 1.25.0
removes the deprecated APIs entirely so this upgrade clears the warnings.
convcoN/A — convco lints messages, it does not generate them
FAQ
Can I use convco and git-agent together?Yes. They serve complementary purposes. Use git-agent to author commits and convco to lint them in CI, generate changelogs, and automate version bumps.
Does git-agent generate changelogs?No. git-agent focuses on authoring high-quality conventional commits. Changelog generation is better handled by dedicated tools like convco, semantic-release, or release-please that read your commit history.
Does convco's hook validate the messages git-agent produces?Yes. Messages produced by git-agent follow the Conventional Commits specification and pass convco's lint rules. git-agent's own pre-commit hook also validates format before each commit.