Update summary generation and prompt templates

* refactor: Modify command summary to generate final summary from prompts and improve flow
* fix: Correct conditional check in helpers.sh for dry-run behavior
* style: Adjust indentation and commenting for clarity
* docs: Update templates/summary_prompt.md to provide clearer instructions for changelog formatting
* feat: Introduce new template for detailed changelog with sections and tags to enhance readability
* chore: Clean up temporary file usage for better resource management

Author: lackeyi

src/giv.sh

@@ -537,10 +537,9 @@ cmd_summary() {
     sum_output_file="${1:-}"
     sum_revision="${2:---current}"
     sum_model_mode="${3:-auto}"
-    sum_dry_run="${4:-}"
+    #sum_dry_run="${4:-}"
 
     summaries_file=$(portable_mktemp "summary_summaries_XXXXXX.md")
-
     summarize_target "${sum_revision}" "${summaries_file}" "${sum_model_mode}"
     print_debug "$(cat "${summaries_file}" || true)"
 
@@ -550,18 +549,13 @@ cmd_summary() {
         exit 1
     fi
 
-    if [ -n "${sum_output_file}" ]; then
-        if [ "${sum_dry_run}" != "true" ]; then
-            cp "${summaries_file}" "${sum_output_file}"
-            printf 'Summary written to %s\n' "${sum_output_file}"
-        else
-            cat "${summaries_file}"
-        fi
-    else
-        cat "${summaries_file}"
-    fi
+    # Generate final summary from summaries
+    prompt_file_name="${PROMPT_DIR}/final_summary_prompt.md"
+    tmp_prompt_file=$(portable_mktemp "final_summary_prompt_XXXXXX.md")
+    build_prompt "${prompt_file_name}" "${summaries_file}" >"${tmp_prompt_file}"
+    print_debug "$(cat "${tmp_prompt_file}" || true)"
+    generate_from_prompt "${tmp_prompt_file}" "${sum_output_file}" "${sum_model_mode}"
 }
-
 cmd_release_notes() {
     summaries_file=$(portable_mktemp "release_notes_summaries_XXXXXX.md")
     summarize_target "${REVISION}" "${summaries_file}" "${model_mode}"

src/helpers.sh

@@ -407,7 +407,7 @@ generate_from_prompt() {
     fi
 
     # 2) Dry‐run?  Just print and exit
-    if [ "${dry_run:-}" = "true" ]; then
+    if [ "${dry_run:-}" = "true" ] || [ -z "${response_output_file}" ]; then
         printf '%s\n' "$res"
         return 0
     fi

templates/final_summary_prompt.md

@@ -0,0 +1,63 @@
+[PROJECT_TITLE] [VERSION]
+[SUMMARY]
+Write a structured, Keep a Changelog–style summary of the provided change summaries.
+
+1. Overview  
+   - Begin with a section summarizing all of the changes, and the purpose and scope of these changes.
+
+2. Change Groups  
+   For each group below (omit any with no entries), include the heading and list bullet points. Each bullet point should prefixed with the type tag:
+
+   ### Added  
+   - Describe each new feature: what changed, why it was added, and its impact.  
+   - Mention affected files or components when relevant.
+
+   ### Fixed  
+   - Describe each bug fix: what was broken, how it’s now resolved, and any side-effects.  
+   - Reference files or tests updated.
+
+   ### Documentation  
+   - Summarize documentation updates: what was clarified or added, and why.
+
+   ### Style  
+   - List formatting or lint changes; note any tooling/formatter updates.
+
+   ### Refactored  
+   - Explain code restructuring: what modules or components were reorganized and benefit gained.
+
+   ### Performance  
+   - Detail optimizations: what was improved and performance gains measured.
+
+   ### Tests  
+   - Outline new or updated tests: what scenarios now covered or fixed.
+
+   ### Build  
+   - Note changes to build scripts, dependencies, or CI configurations.
+
+   ### CI/CD  
+   - Summarize pipeline/job changes or additions.
+
+   ### Chores  
+   - Miscellaneous maintenance tasks not covered above.
+
+   ### Security  
+   - Describe any security patches or vulnerability fixes.
+
+3. Formatting & Tone  
+   - Use bullet points (`- `) under each heading  
+   - Write in natural, professional language—avoid raw diff syntax.  
+   - Group related items together and maintain logical order.
+   - Do not include groups with no related items.
+   - Each list item should provide enough detail to understand the change.
+
+4. Processing Instructions  
+   - Review the provided change summaries.  
+   - Assign changes to the appropriate group above.  
+   - Extract file paths or components when pertinent.  
+   - If possible, explain "what" changed, "why," and the "impact."
+   - Only use information provided in this content in your response.
+   - Consolidate related changes from different summaries to avoid duplicating information.
+   - Determine if older changes have been superseded and use only the latest information.
+
+[EXAMPLE]
+[RULES]

templates/summary_prompt.md

@@ -48,15 +48,15 @@ Write a structured, Keep a Changelog–style summary of the provided git diff. D
    - Keep each bullet under 120 characters.  
    - Write in natural, professional language—avoid raw diff syntax.  
    - Group related items together and maintain logical order.
+   - Do not include groups with no related items.
    - Each list item should provide enough detail to understand the change.
 
 4. Processing Instructions  
    - Parse the git diff to detect each change’s type.  
    - Assign changes to the appropriate group above.  
    - Extract file paths or components when pertinent.  
-   - If possible, explain "what" changed, "why," and the "impact." 
-   - Only use information provided in this content in your response. 
+   - If possible, explain "what" changed, "why," and the "impact."
+   - Only use information provided in this content in your response.
 
 [EXAMPLE]
 [RULES]
-