From 05d94e264695d5f60666c00f05ea4ea0284c0645 Mon Sep 17 00:00:00 2001 From: Jeremy Dormitzer Date: Wed, 24 Jul 2024 10:42:04 -0400 Subject: [PATCH] Refines commit message prompt directive Updated the guidelines for generating commit messages to avoid using the word 'enhance' and user experience references, and request plain text responses without syntax. --- emacs/.emacs.d/config/init-ai.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/emacs/.emacs.d/config/init-ai.el b/emacs/.emacs.d/config/init-ai.el index 4ffc29b..74adce7 100644 --- a/emacs/.emacs.d/config/init-ai.el +++ b/emacs/.emacs.d/config/init-ai.el @@ -61,7 +61,7 @@ (goto-char (point-max)) (forward-line -1) (point))))) - (prompt (format "%s\n\nWrite a clear, concise commit message for this diff. The first line should succinctly summarize the changes made and should be no more than 50 characters. If additional context is needed, include it in an additional paragraph separate by a blank line from the first line. Reply with the commit message only." diff))) + (prompt (format "%s\n\nWrite a clear, concise commit message for this diff. The first line should succinctly summarize the changes made and should be no more than 50 characters. If additional context is needed, include it in an additional paragraph separate by a blank line from the first line. Do not use the word 'enhance' or talk about the user experience. Reply in plain text with no Markdown or other syntax. Reply with the commit message only." diff))) (message "Generating commit message...") (gptel-request prompt :stream t