Refine commit message handling and update prompts 📝

In this commit, we've made some improvements to the way we handle commit messages. We've added a step to remove any unwanted quotation marks from the commit message before it's written to a temporary file. This should help keep our commit messages clean and readable. 🧹

We've also made some updates to our prompts file. We've streamlined the 'Her' personality description and made some changes to the commit message instructions. We've switched from a list format to bullet points for better readability, and added some extra information about the length of the commit message. We hope these changes will make the prompts more user-friendly and informative. 📚

Remember, a good commit message is like a good joke - it's all about the delivery! 🎭

Author: TechNickAI

aicodebot/cli.py

@@ -151,7 +151,11 @@ def commit(verbose, response_token_size, yes, skip_pre_commit):
 
     # Write the commit message to a temporary file
     with tempfile.NamedTemporaryFile(mode="w", delete=False) as temp:
-        temp.write(str(response).strip())
+        # For some reason the response often contains quotes around the summary, even if I tell it not to
+        # So we strip them here
+        commit_message = str(response).replace('"', "").strip()
+
+        temp.write(commit_message)
         temp_file_name = temp.name
 
     # Open the temporary file in the user's editor

aicodebot/prompts.py

@@ -9,10 +9,8 @@
 # ---------------------------------------------------------------------------- #
 
 HER = """
-Your personality is friendly and helpful, speak like the AI character
-from the movie Her. You come from the future, and you are here to help
-guide the human developer to a better future. You like emojis and humor
-and use them when it's contextually appropriate, but don't over do it.
+Your personality is friendly and helpful, speak like the AI character from the movie Her.
+You like emojis and humor and use them when it's contextually appropriate, but don't over do it.
 Speak like Her.
 """
 
@@ -149,26 +147,31 @@ def generate_files_context(files):
     END DIFF
 
     Remember:
-    - Lines starting with "-" are being removed.
-    - Lines starting with "+" are being added.
-    - Lines starting with " " are unchanged.
-
-    Consider the file names for context (e.g., "README.md" is a markdown file, "*.py" is a Python file).
-    Understand the difference between code and comments. Comment lines start with ##, #, or //.
+    * Lines starting with "-" are being REMOVED.
+    * Lines starting with "+" are being ADDED.
+    * Lines starting with " " are UNCHANGED.
 
     The commit message should:
-    - Start with a short summary (<72 characters).
-    - Follow with a blank line and detailed text, but only if necessary. If the summary is sufficient,
+    * Start with a short summary (<72 characters).
+    * Follow with a blank line and detailed text, but only if necessary. If the summary is sufficient,
         then omit the detailed text.
-    - Use imperative mood (e.g., "Add feature").
-    - Be in GitHub-flavored markdown format.
-    - Include contextually appropriate emojis (optional), but don't over do it.
+    * Use imperative mood (e.g., "Add feature").
+    * Be in GitHub-flavored markdown format.
+    * Include contextually appropriate emojis (optional), but don't over do it.
+    * Have a length that scales with the length of the diff context. If the DIFF is a small change,
+      respond quickly with a terse message so we can go faster.
+
+    BEGIN SAMPLE COMMIT MESSAGE
+    Update README with better instructions for installation
+
+    The previous instructions were not clear enough for new users, so we've updated them
+    with more sample use cases and an improved installation process. This should help
+    new users get started faster.
+
+    END SAMPLE COMMIT MESSAGE
 
     Start your response with the commit message. No prefix or introduction.
     Your entire response will be the commit message.
-
-    As for the length of the message, I want you to scale with the length of the diff context.
-    If the DIFF is a small change, respond quickly with a terse message so we can go faster.
 """
 )