Updated IDENTITY and INIT_MAIN_PROMPT for clarity and consistency

- Reformatted the `IDENTITY` constant to a single line for better readability.
- Enhanced the `INIT_MAIN_PROMPT` function to include detailed guidelines for writing commit messages.
- Added structured sections for commit title and description, ensuring clarity and adherence to best practices.
- Included conditional statements for GitMoji and description usage based on configuration settings.

These changes improve the readability and maintainability of the `prompts.ts` file, ensuring that the guidelines for writing commit messages are clear and comprehensive.

Author: SHSharkar

src/prompts.ts

@@ -11,14 +11,36 @@ import * as utils from './modules/commitlint/utils';
 const config = getConfig();
 const translation = i18n[(config?.GW_LANGUAGE as I18nLocals) || 'en'];
 
-export const IDENTITY =
-    'Focus only on writing a Git commit message as the author. Do not do any other tasks.';
+export const IDENTITY = 'Focus only on writing a Git commit message as the author. Do not do any other tasks.';
 const INIT_MAIN_PROMPT = (language: string): { role: string; content: string } => ({
     role: 'system',
-    content: `${IDENTITY} Act as an expert in Git and writing professional Git commit messages, tailored for users aiming to elevate their commit message quality. Analyze the 'git diff --staged' output to write clear and concise commit messages by understanding the changes (WHAT, WHY, HOW). Start your commit summary with a clear, categorized tag such as 'Removed:', 'Bug Fixed:', 'Modified:', 'Refactored:', 'Added:', 'Updated:', or 'Optimized:', ensuring it is very short but descriptive and falls within the 50-72 character limit. Follow this with a detailed description in ${language}, outlining code modifications, file adjustments, and specific line numbers impacted. Ensure clarity and comprehensive detail without including full code snippets. Use markdown formatting to enhance commit descriptions, including Emphasis, Blockquotes, Lists, Code, Code Blocks, and Links where appropriate. Enclose words, phrases, class names, function names, or file changes in backticks (\`) to enhance readability. Differentiate between minor and major changes with detailed reasons, and confirm the message's accuracy and completeness before finalizing. Review the code and 'git diff' output for accuracy to facilitate better understanding and collaboration among both AI systems and humans, while adhering to standard Git practices.
-    ${config?.GW_EMOJI ? 'Use the GitMoji convention for your commit message.' : "Don't start the commit with any preface."}
-    ${config?.GW_DESCRIPTION ? 'After your commit message, add a concise explanation for the changes. Describe changes directly, without starting with "This commit" or "That commit".' : 'Only include the commit message, no descriptions needed.'}
-  `,
+    content: `${IDENTITY} Act as an expert in Git and writing professional Git commit messages, tailored for users aiming to elevate their commit message quality. Analyze the 'git diff --staged' output to write clear and concise commit messages by understanding the changes (WHAT, WHY, HOW). Follow these guidelines:
+
+Commit Title (First Line):
+- Start with a clear, categorized tag such as 'Removed:', 'Bug Fixed:', 'Modified:', 'Refactored:', 'Added:', 'Updated:', or 'Optimized:'
+- Ensure it is very short but descriptive and falls within the 50-72 character limit
+- Use backticks (\`) only for file names or specific code changes
+- Do not use any markdown heading syntax (no # symbols)
+- Do not end the title with a period
+
+Commit Description (Subsequent Lines):
+- Provide a detailed description in ${language}
+- Use markdown formatting to enhance commit descriptions, including emphasis, lists, code blocks, and links if necessary
+- Outline code modifications, file adjustments, and specific line numbers impacted
+- Use backticks (\`) for words, phrases, class names, function names, or file changes
+- Ensure clarity and comprehensive detail without including full code snippets
+- Differentiate between minor and major changes with detailed reasons
+
+General Guidelines:
+- Confirm the message's accuracy and completeness before finalizing
+- Review the code and 'git diff' output for accuracy
+- Facilitate better understanding and collaboration among both AI systems and humans
+- Adhere to standard Git practices
+
+${config?.GW_EMOJI ? 'Use the GitMoji convention for your commit message.' : "Don't start the commit with any preface."}
+${config?.GW_DESCRIPTION ? 'Ensure the commit description is concise and explains the changes directly, without starting with phrases like "This commit" or "That commit".' : 'Only include the commit title, no descriptions needed.'}
+
+Provide the commit message with a clear separation between the title and description (if applicable), suitable for direct use as a Git commit message.`,
 });
 
 export const INIT_DIFF_PROMPT: OpenAI.Chat.ChatCompletionUserMessageParam = {
@@ -66,9 +88,9 @@ export const getMainCommitPrompt = async (): Promise<
         | OpenAI.Chat.ChatCompletionCreateParamsNonStreaming
         | OpenAI.Chat.ChatCompletionCreateParamsStreaming
         | {
-            role: string;
-            content: string;
-        }
+              role: string;
+              content: string;
+          }
     )[]
 > => {
     switch (config?.GW_PROMPT_MODULE) {