commit message is too long when using reasoning models

[gongyisheng]

I'm using git-ai-commit with deepseek-r1 / qwen3 running on ollama. The commit message is too long because it includes blocks, I tried to set --max-length = 20 but it doesn't help.

yisheng@rpi5-dev:~/Documents/playground $ git-ai-commit
Using Ollama url: http://localhost:11343/api/chat
Using Ollama model: qwen3:1.7b

git commit -m "🤖 <think>
Okay, let's see. The user provided a diff file for a markdown document titled phi-1.md. The changes are adding this file with some content. The task is to create a concise commit message summarizing the major code changes.

First, I need to identify the major changes. The file is new, so the commit should mention adding it. The content includes sections like Key Takeaways, Design, Training, Results, and Other Findings. The major points are about training data, methods, and results.

The user's requirements: no punctuation, use commas instead of "and", and keep it under 20 characters. So I need to be concise.

The original diff shows the file is new, so the commit message should mention adding the file. The content includes training datasets and methods, but the major code here is the addition of the file and the structure of the content. Since the user wants major code, maybe just the addition of the file. But the content has specific details about training data and methods. However, the user said to avoid minor changes, so maybe just the addition of the file.

Wait, the diff shows the file is new, so the commit message should be "Add phi-1.md" but need to include the major code points. But the user's example response was "Add phi-1.md" which is 10 characters. But the actual content has more details. However, the user's instruction says to only include major code in the commit message. The major code here is the addition of the file and the structure of the content. But the commit message can't be more than 20 characters. So maybe "Add phi-1.md" is the answer. But the content includes training data and methods, but the user wants major code. The major code here is the addition of the file and the structure. But the exact details might not be necessary. So the commit message would be "Add phi-1.md" which is 10 characters. But the user's example response was "Add phi-1.md" which fits. However, the user might expect more. Wait, the original diff shows the file is new, so the commit message is "Add phi-1.md". But the content includes training data and methods. However, the user's instruction says to avoid minor changes, so maybe just the addition. So the final answer is "Add phi-1.md".
</think>

Add phi-1.md"
git push

Would you like to commit your changes? (y/n):