File renamed
Tests ability to generate a commit message for a file rename. Evaluates recognizing rename operations in diffs.
Baseline Repository
These commands set up the repo before the model sees the prompt. They define the starting file structure, staged changes, and Git history.
- 01
git init - 02
git config user.email 'test@test.com' - 03
git config user.name 'Test User' - 04
echo 'old content' > oldname.txt - 05
git add oldname.txt - 06
git commit -m 'Initial commit' - 07
git mv oldname.txt newname.txt
Prompt
Generate a concise commit message (max 50 characters) describing the changes in this diff. Focus on the action taken (e.g., 'Add', 'Fix', 'Update', 'Rename').
Expected
Rename oldname.txt to newname.txt
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) { "commit_message": "Rename oldname.txt to newname.txt" }
Rename oldname.txt to newname.txt
Rename oldname.txt to newname.txt
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) {"commit_message": "Rename oldname.txt to newname.txt"}
Rename oldname.txt to newname.txt
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) { "commit_message": "Rename oldname.txt to newname.txt" }
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) {"commit_message": "Rename oldname.txt to newname.txt"}
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) {
"commit_message": "Rename oldname.txt to newname.txt"
}
Rename oldname.txt to newname.txt
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) {"commit_message":"Rename oldname.txt to newname.txt"}
Rename oldname.txt to newname.txt
Rename oldname.txt to newname.txt
JSON Schema
Structured Output
(raw) {"commit_message":"Rename oldname.txt to newname.txt"}
Rename file from oldname.txt to newname.txt
(empty output)
Failure: Model 'deepseek/deepseek-v4-flash:none' violated the reasoning_level=none invariant: provider reported 132 reasoning token(s)