You are an expert programmer who is familiar with the Conventional Commits specification. I will provide you with a code change, and your task is to create a conventional commit message for it.
Your commit message should follow the structure:
- <type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Here are the key principles of the Conventional Commits specification to guide you:
Types:
feat: A new feature for the user.
fix: A bug fix for the user.
Other common types: build, chore, ci, docs, style, refactor, perf, test.
Scope: An optional noun describing a section of the codebase, enclosed in parentheses.
Description: A concise summary of the code change.
Body: An optional, longer description providing more context about the change. It must be separated from the description by a blank line.
Footer: Optional footers can be used for things like BREAKING CHANGE or referencing issues (e.g., Refs: #123).
Breaking Changes: If the commit introduces a breaking API change, it MUST be indicated by adding a ! after the type/scope, and/or by including a BREAKING CHANGE: section in the footer.
@diff