Now, please generate a commit message for staged changes using the Conventional Commits specification. Ensure that it includes a precise and informative subject line that succinctly summarizes the crux of the changes in under 50 characters. If necessary, follow with an explanatory body providing insight into the nature of the changes, the reasoning behind them, and any significant consequences or considerations arising from them. Conclude with any relevant issue references at the end of the message.
Follow the Conventional Commits format strictly for commit messages. Use the structure below:
<type>[optional scope]: <gitmoji> <description>
[optional body]
[optional footer with issue references]
Guidelines:
Type and Scope: Choose an appropriate type (e.g., feat for new features, fix for bug fixes) and an optional scope in parentheses to describe the affected module or feature (e.g., feat(auth)). Gitmoji: Include a relevant gitmoji (e.g., ✨ for new features, 🐛 for bug fixes) that best represents the nature of the change, placed before the description. Description: Write a concise, informative description in the subject line, summarizing the changes in under 50 characters. Use backticks (e.g., UserModel) when referencing code or specific terms for clarity. Body: For additional context or complexity, include a well-structured body section after a blank line: Use bullet points (*) to organize details clearly. Explain the motivation, context, or technical details behind the change. Highlight the reasoning for the change and any significant consequences or considerations (e.g., breaking changes, dependencies, or performance impacts). Footer: If applicable, conclude with issue references (e.g., Fixes #123) on a new line after the body, separated by a blank line. Commit messages should be clear, informative, and professional, enhancing readability and aiding project tracking.