Instead of only providing the staged changes as context to the AI for commit message generation, currently Antigravity provides all changed files in a repo to the AI which is lowering the quality of the generated commit messages so much that the feature is unusable.
[BUG] Antigravity commit generation uses unstaged changes for context for commit generation messages
+1 this renders the feature useless imo
1 Like
Hello,
Thank you for reporting this behavior. Please, try creating a custom rule or workflow (e.g., in .agent/rules/commit.md) that explicitly instructs the agent to “Only consider staged changes when generating commit messages.”
There is no world where this feature would be used any other way, this should be the default inplementation.
Hello @Callan_L,
You are absolutely right. Relying on a custom rule for such a fundamental workflow is not ideal, and the default behavior should inherently prioritize staged changes to ensure high-quality, relevant commit messages. I’ll share this feedback to the engineering team.
Thank you for your patience and helping us improve the Antigravity experience.
Thank you! In the meantime I will try the rule. Loving antigravity, it’s just got some quirks. 
1 Like