Writing good commit messages is the chore every developer knows they should do but often skips. “fixed stuff” or “update” litter the history of every project.
Gitlawb Zero just fixed this with a single flag: --auto.
How It Works
When you stage your changes and run zero --auto, the agent:
- Reads the
git diff --stagedoutput - Analyzes what changed and why
- Generates a conventional commit message with type, scope, and description
- Applies it via
git commit -m
The result is messages like:
feat(auth): add OAuth token refresh flow for ChatGPT integration
fix(tui): keep profile name on /model switch so stored key resolves
docs(install): recommend bun pm trust for Bun installsEach message follows conventional commits format, making them useful for changelog generation and semantic versioning.
The Implementation
The --auto flag (PR #423) works through Zero’s existing git integration. It doesn’t replace your editor — it augments it. You can still write custom messages for important commits, but for the routine ones, --auto handles it.
The flag is model-agnostic. Zero uses whatever provider you have configured to generate the message, so the quality scales with your model choice.
Why This Matters
Git commit messages are the #1 most neglected documentation artifact in software engineering. Everyone agrees they’re important. Few people write them well. An AI agent that generates high-quality commit messages from diffs solves this permanently.
Zero’s --auto flag is one of several AI-assisted commit message tools. Claude Code has a /commit command that generates messages from diffs and matches repo style. OpenCode has community plugins like opencode-conventional-commits and gen-commit-msg for the same workflow. Hermes has PR automation features.
What makes Zero’s --auto different is the tight TUI integration — you don’t need a separate plugin or slash command. It’s built into the core zero commit flow.
This is one of those features that seems obvious once you see it.