Add AI-powered commit message generation script

[guibranco]

User description

Closes #

📑 Description

✅ Checks

• [ ] My pull request adheres to the code style of this project
• [ ] My code requires changes to the documentation
• [ ] I have updated the documentation as required
• [ ] All the tests have passed

☢️ Does this introduce a breaking change?

• [ ] Yes
• [ ] No

ℹ Additional Information

---

Description

• Introduced a new script for generating AI-powered commit messages using dotnet-aicommitmessage.
• The script includes checks for the presence of the required tool and handles errors gracefully.
• Users can bypass the script by setting the GIT_AICOMMIT_SKIP environment variable.

---

Changes walkthrough 📝

	Relevant files
Enhancement	prepare-commit-msg Add AI-powered commit message generation script                    .githooks/prepare-commit-msg Added a script to generate AI-powered commit messages. Includes error handling for missing dependencies and empty messages. Allows bypassing the script via an environment variable. +32/-0

---

💡 Penify usage: Comment /help on the PR to get a list of all available Penify tools and their descriptions

[penify-dev[bot]]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the script is straightforward and primarily involves shell scripting with basic error handling.
🧪 Relevant tests	No
⚡ Possible issues	Error Handling: The script does not handle cases where the `git diff --staged` command fails, which could lead to unexpected behavior.
	Hardcoded Branch Name: The branch name is hardcoded as "branch-name", which may not be appropriate for all use cases.
🔒 Security concerns	No

[penify-dev[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Add validation for the commit message file to ensure it is provided and valid ___ **Ensure that the script checks if the COMMIT_MSG_FILE variable is set and is a valid file before proceeding to avoid potential errors.** [.githooks/prepare-commit-msg [17]](https://github.com/guibranco/gstraccini-bot-api/pull/12/files#diff-dcfff605ffad618dd937de6369eb0e61d25656d8e2a0ba5ed3546b025c39678dR17-R17) ```diff -COMMIT_MSG_FILE=$1 +if [ -z "$1" ] || [ ! -f "$1" ]; then echo "Error: Commit message file is not provided or does not exist." >&2; exit 1; fi; COMMIT_MSG_FILE=$1 ``` Suggestion importance[1-10]: 9 Why: This suggestion addresses a potential issue that could lead to runtime errors, making it crucial for the script's robustness.	9
Enhancement	Use the current branch name dynamically instead of a hardcoded value ___ **Instead of hardcoding "branch-name", consider using a command to dynamically fetch the current branch name for better accuracy.** [.githooks/prepare-commit-msg [22]](https://github.com/guibranco/gstraccini-bot-api/pull/12/files#diff-dcfff605ffad618dd937de6369eb0e61d25656d8e2a0ba5ed3546b025c39678dR22-R22) ```diff -AI_MESSAGE=$(dotnet-aicommitmessage generate-message -m "$CURRENT" -b "branch-name" -d "$GIT_DIFF" ) +AI_MESSAGE=$(dotnet-aicommitmessage generate-message -m "$CURRENT" -b "$(git rev-parse --abbrev-ref HEAD)" -d "$GIT_DIFF" ) ``` Suggestion importance[1-10]: 8 Why: This suggestion enhances the script's accuracy by dynamically fetching the branch name, which is important for correct functionality.	8
Maintainability	Improve the error message for clarity on AI message generation failures ___ **Consider using a more specific error message for when the AI message generation fails, indicating that the issue might be with the input or the tool itself.** [.githooks/prepare-commit-msg [23]](https://github.com/guibranco/gstraccini-bot-api/pull/12/files#diff-dcfff605ffad618dd937de6369eb0e61d25656d8e2a0ba5ed3546b025c39678dR23-R23) ```diff -echo "Error: Failed to generate AI commit message. Using original message." >&2 +echo "Error: AI message generation failed. Please check the input and ensure dotnet-aicommitmessage is functioning correctly." >&2 ``` Suggestion importance[1-10]: 7 Why: The suggestion improves clarity in error messaging, which is beneficial for debugging, but it does not address a critical issue.	7
Best practice	Specify the shell in the shebang for consistent script execution ___ **Consider adding a shebang line for a specific shell (e.g., #!/bin/bash) to ensure consistent behavior across different environments.** [.githooks/prepare-commit-msg [1]](https://github.com/guibranco/gstraccini-bot-api/pull/12/files#diff-dcfff605ffad618dd937de6369eb0e61d25656d8e2a0ba5ed3546b025c39678dR1-R1) ```diff -#!/bin/sh +#!/bin/bash ``` Suggestion importance[1-10]: 6 Why: While specifying the shell can improve consistency, it is a minor improvement and does not significantly impact the script's functionality.	6