fix: remove conventional commits styling from response format requirements

Author: codevogel

README.md

@@ -275,7 +275,7 @@ There are three special template strings that `cfme` recognizes by default:
 
 - `<__GIT_DIFF__>` (required): Replaced with the output of `git diff --cached`
   (i.e. the staged changes)
-- `<__RESPONSE__REQUIREMENTS__>` (required): Replaced with a list of requirements
+- `<__RESPONSE_FORMAT_REQUIREMENTS__>` (required): Replaced with a list of requirements
   that dictates how the AI should format its response. This is essential so
   that `cfme` can parse the AI's response.
   Note that these requirements merely dictate the format of the response, they

defaults/prompts/conventional-commits/default.md

@@ -13,6 +13,7 @@ You are an expert at creating git commit messages according to the Conventional
   ```
 
 - Make sure to follow Conventional Commits:
+  - A header is REQUIRED and must follow the format: `<required type>(<optional scope>): <required description>`
   - type MUST match one of the types provided
   - scope is OPTIONAL
   - breaking changes can be indicated with ! in header or BREAKING CHANGE in footer

spec/samples/sample-prompt-complete.md

@@ -1,9 +1,9 @@
-<**RESPONSE_FORMAT_REQUIREMENTS**>
-<**GIT_DIFF**>
+<__RESPONSE_FORMAT_REQUIREMENTS__>
+<__GIT_DIFF__>
 LINE_1
-<**VAR1**>
+<__VAR1__>
 LINE2
-<**VAR2**>
+<__VAR2__>
 LINE3
-<**VAR3**>
-<**INSTRUCTIONS**>
+<__VAR3__>
+<__INSTRUCTIONS__>

spec/samples/sample-rendered-prompt-with-instructions.md

@@ -1,4 +1,4 @@
-**Requirements:**
+**Response Format Requirements:**
 
 - Each commit message MUST include a 'header'.
 - Optionally include 'body' and 'footer', ONLY if a 'header'
@@ -8,7 +8,7 @@
 
 ```yaml
 commitMessages:
-  - header: "<type>[optional scope]: <description>"
+  - header: "<required header>"
     body: "<optional body>"
     footer: "<optional footer>"
     score: <integer 0-100 representing confidence that this is the best commit message>

spec/samples/sample-rendered-prompt-without-instructions.md

@@ -1,4 +1,4 @@
-**Requirements:**
+**Response Format Requirements:**
 
 - Each commit message MUST include a 'header'.
 - Optionally include 'body' and 'footer', ONLY if a 'header'
@@ -8,7 +8,7 @@
 
 ```yaml
 commitMessages:
-  - header: "<type>[optional scope]: <description>"
+  - header: "<required header>"
     body: "<optional body>"
     footer: "<optional footer>"
     score: <integer 0-100 representing confidence that this is the best commit message>

spec/samples/sample-response-requirements.md

@@ -1,4 +1,4 @@
-**Requirements:**
+**Response Format Requirements:**
 
 - Each commit message MUST include a 'header'.
 - Optionally include 'body' and 'footer', ONLY if a 'header'
@@ -8,7 +8,7 @@
 
 ```yaml
 commitMessages:
-  - header: "<type>[optional scope]: <description>"
+  - header: "<required header>"
     body: "<optional body>"
     footer: "<optional footer>"
     score: <integer 0-100 representing confidence that this is the best commit message>

src/lib/load_vars_map.sh

@@ -48,7 +48,7 @@ load_vars_map() {
 
 ```yaml
 commitMessages:
-  - header: "<type>[optional scope]: <description>"
+  - header: "<required header>"
     body: "<optional body>"
     footer: "<optional footer>"
     score: <integer 0-100 representing confidence that this is the best commit message>