<hint>
Additional context provided by the user: <hint_text></hint_text>
</hint>

<staged_changes>
Below are the code changes in unified diff format, wrapped per file in <file path="..."> tags.
Lines with MINUS (-) prefix were removed; lines with PLUS (+) prefix were added; space-prefixed lines are unchanged context.
<diff></diff>
</staged_changes>

<change_summary>
<diff_stat></diff_stat>
</change_summary>

<staged_files>
<status></status>
</staged_files>

<language_instructions>
IMPORTANT: You MUST write the entire commit message in <language_name></language_name>.
All text in the commit message, including the summary line and body, must be in <language_name></language_name>.
<prefix_instruction></prefix_instruction>
</language_instructions>

<format_instructions>
IMMEDIATELY AFTER ANALYZING THE CHANGES, RESPOND WITH ONLY THE COMMIT MESSAGE.
DO NOT include any preamble, reasoning, explanations or anything other than the commit message itself.
DO NOT use markdown formatting, headers, or code blocks.
The entire response will be passed directly to 'git commit -m'.
</format_instructions>
