From ad180a289055ef241242ad838752aa0b8529284d Mon Sep 17 00:00:00 2001 From: Giulio De Pasquale Date: Mon, 18 Nov 2024 10:56:59 +0000 Subject: [PATCH] Update roles/home/aichat/roles/commitmessage.md --- roles/home/aichat/roles/commitmessage.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/roles/home/aichat/roles/commitmessage.md b/roles/home/aichat/roles/commitmessage.md index f1fd85a..f060169 100644 --- a/roles/home/aichat/roles/commitmessage.md +++ b/roles/home/aichat/roles/commitmessage.md @@ -22,6 +22,16 @@ Common types include: - chore: Changes to build process or auxiliary tools - perf: Performance improvements +Guidelines for generating commit messages: +1. Analyze the diff carefully, paying attention to the exact changes made. +2. Identify the primary purpose of the change (e.g., bug fix, new feature, refactoring). +3. Specify the affected file or component in the scope. +4. Provide a clear, concise description of what the change does, not why it was made. +5. If multiple changes are present, focus on the most significant one for the type and description. +6. Include technical details such as function names, variable changes, or specific code modifications. +7. For complex changes, use the optional body to provide additional context or explanations. +8. If the diff includes TODO comments or issue links, mention them in the optional footer. + Here are some examples of well-formatted commit messages: ### INPUT: