git_commit.hbs

Project Path: {{ absolute_code_path }}

Please generate a git commit message for the provided `git diff` output.

Source Tree:
```
{{ source_tree }}
```

## Diff

{{#if git_diff}}
Diff:
```
{{git_diff}}
```
{{/if}}

## Request

Make sure to thoroughly analyze the git diff output in order to understand its purpose, that is crucial to generating the highest quality commit message. The git commit should have the following attributes:

1. Concise Subject: Short and informative subject line, less than 50 characters.
2. Descriptive Body: Optional summary of 1 to 2 sentences, wrapping at 72 characters.
3. Use Imperative Mood: For example, "Fix bug" instead of "Fixed bug" or "Fixes bug."
4. Capitalize the Subject: First letter of the subject should be capitalized.
5. No Period at the End: Subject line does not end with a period.
7. Separate Subject From Body With a Blank Line: If using a body, leave one blank line after the subject.

Write the content in Markdown format. Try to stick to what can be learned and inferred from the diff output itself. However, let me know if additional context is needed. The commit message should make be clear enough that an outside contributor can quickly scan the commit message and diff output and understand what happened and what was changed or fixed through that particular commit.