Refactor logging and build prompt functionality

* feat: Add output file logging in parse_args
* feat: Include project title in prompt generation
* fix: Handle missing version gracefully in build_prompt
* chore: Clean up variable assignments in build_prompt
* chore: Enhance prompt content by appending final instructions

Author: lackeyi

src/giv.sh

@@ -366,7 +366,6 @@ parse_args() {
     print_debug "  Template Directory: ${template_dir}"
     print_debug "  Config File: ${config_file}"
     print_debug "  Config Loaded: ${is_config_loaded}"
-    print_debug "  Output File: ${output_file}"
     print_debug "  TODO Files: ${todo_files}"
     print_debug "  TODO Pattern: ${todo_pattern}"
     print_debug "  Version File: ${version_file}"
@@ -375,6 +374,7 @@ parse_args() {
     print_debug "  Model Mode: ${model_mode}"
     print_debug "  API Model: ${api_model}"
     print_debug "  API URL: ${api_url}"
+    print_debug "  Output File: ${output_file}"
     print_debug "  Output Mode: ${output_mode}"
     print_debug "  Output Version: ${output_version}"
     print_debug "  Prompt File: ${prompt_file}"
@@ -593,8 +593,12 @@ cmd_announcement() {
 
     prompt_file_name="${PROMPT_DIR}/announcement_prompt.md"
     tmp_prompt_file=$(portable_mktemp "announcement_prompt_XXXXXX.md")
-    build_prompt "${prompt_file_name}" "${summaries_file}" >"${tmp_prompt_file}"
+    project_title="$(parse_project_title "${summaries_file}")"
+    print_debug "Project title: ${project_title}"
+    build_prompt --project-title "${project_title}" "${prompt_file_name}" "${summaries_file}" >"${tmp_prompt_file}"
 
+    print_debug "Generated prompt file: ${tmp_prompt_file}"
+    print_info "$(cat "${tmp_prompt_file}" || true)"
     generate_from_prompt "${tmp_prompt_file}" \
         "${output_file:-${announce_file}}" "${model_mode}"
 }

src/helpers.sh

@@ -110,10 +110,17 @@ replace_tokens() {
 # Exports GIV_TOKEN_SUMMARY (and any of PROJECT_TITLE, VERSION, EXAMPLE, RULES
 # if passed) then runs replace_tokens on the template.
 build_prompt() {
-    project_title=$(parse_project_title)
-    version="${GIV_TOKEN_VERSION:-}"
-    example="${GIV_TOKEN_EXAMPLE:-}"
-    rules="${GIV_TOKEN_RULES:-}"
+    project_title="$(parse_project_title)"
+
+    version="${output_version:-${GIV_TOKEN_VERSION:-}}"
+    if [ -z "${version}" ] || [ "${version}" = "auto" ]; then
+        print_debug "No version set or version is 'auto', trying to find it from version file"
+        # Try to find the version file and extract the version
+        version_file="$(find_version_file)"
+        version="$(get_version_info --current "${version_file:-}")"
+    fi
+    example=""
+    rules=""
     # parse flags
     while [ $# -gt 2 ]; do
         case "$1" in
@@ -156,13 +163,19 @@ build_prompt() {
     # export our tokens
     export GIV_TOKEN_SUMMARY
     GIV_TOKEN_SUMMARY=$(cat "${diff_file}")
-    [ -n "$project_title" ] && export GIV_TOKEN_PROJECT_TITLE="$project_title"
-    [ -n "$version" ] && export GIV_TOKEN_VERSION="$version"
-    [ -n "$example" ] && export GIV_TOKEN_EXAMPLE="$example"
-    [ -n "$rules" ] && export GIV_TOKEN_RULES="$rules"
 
-    # run the replacement
-    replace_tokens <"$prompt_template"
+    export GIV_TOKEN_PROJECT_TITLE="${project_title:-${GIV_TOKEN_PROJECT_TITLE}}"
+    export GIV_TOKEN_VERSION="${version:-${GIV_TOKEN_VERSION}}"
+    export GIV_TOKEN_EXAMPLE="${example:-${GIV_TOKEN_EXAMPLE}}"
+    export GIV_TOKEN_RULES="${rules:-${GIV_TOKEN_RULES}}"
+
+    # Append the extra instructions to the prompt content before passing to replace_tokens
+    {
+        cat "${prompt_template}"
+        printf '\nOutput just the final content—no extra commentary or code fencing. '
+        printf 'Use only information contained in this prompt and the summaries provided above.'
+    } | replace_tokens
+    return
 }
 
 # Locate the project from the codebase. Looks for common project files

templates/announcement_prompt.md

@@ -1,3 +1,5 @@
+# Summary of Changes
+
 [SUMMARY]
 
 Write one engaging blog post announcing the [VERSION] release of [PROJECT_TITLE], using the following guidelines:
@@ -37,6 +39,4 @@ Write one engaging blog post announcing the [VERSION] release of [PROJECT_TITLE]
    • Craft a narrative that flows logically from introduction to CTA  
    • Ensure all technical details are translated into user-friendly language  
 
-Output just the final blog post—no extra commentary and using only information from the summaries provided above.
-
-[RULES]
+[RULES]

templates/changelog_prompt.md

@@ -1,4 +1,9 @@
+# Summary of Changes
+
 [SUMMARY]
+
+## Task
+
 Generate a comprehensive changelog in the Keep a Changelog format for [PROJECT_TITLE] [VERSION]:
 
 1. Format Requirements:
@@ -32,12 +37,13 @@ Generate a comprehensive changelog in the Keep a Changelog format for [PROJECT_T
 
 [EXAMPLE]
 
-Processing Instructions:
+## Processing Instructions
+
 - Analyze all provided summaries
 - Identify release boundaries
 - Group changes by type
 - Maintain chronological order
 - Ensure consistent formatting
 - Focus on technical accuracy
 
-[RULES]
+[RULES]

templates/message_prompt.md

@@ -1,4 +1,9 @@
+## Summary of Changes
+
 [SUMMARY]
+
+## Instructions
+
 Write a git commit message for the provided git history following the Keep a Changelog standard:
 
 1. Format Requirements:
@@ -40,3 +45,4 @@ Write a git commit message for the provided git history following the Keep a Cha
 
 [EXAMPLE]
 
+[RULES]

templates/post_example.md

@@ -0,0 +1,9 @@
+```
+🚀 BIG NEWS! 🚀
+We've just released v1.2.3 with game-changing authentication improvements! 🛡️
+✨ 50% faster login times
+✨ Enhanced security with JWT tokens
+✨ Seamless cross-platform experience
+
+Read the full announcement and upgrade now! [link] #SoftwareRelease #NewFeatures #PerformanceMatters
+```

templates/post_prompt.md

@@ -1,4 +1,9 @@
+## Summary of Changes
+
 [SUMMARY]
+
+## Instructions
+
 Generate an engaging social media post announcing the [PROJECT_TITLE] [VERSION] release:
 
 1. Content Requirements:
@@ -31,15 +36,7 @@ Generate an engaging social media post announcing the [PROJECT_TITLE] [VERSION]
 
 5. Example Format:
 
-```
-🚀 BIG NEWS! 🚀
-We've just released v1.2.3 with game-changing authentication improvements! 🛡️
-✨ 50% faster login times
-✨ Enhanced security with JWT tokens
-✨ Seamless cross-platform experience
-
-Read the full announcement and upgrade now! [link] #SoftwareRelease #NewFeatures #PerformanceMatters
-```
+[EXAMPLE]
 
 6. Processing Instructions:
 
@@ -49,4 +46,4 @@ Read the full announcement and upgrade now! [link] #SoftwareRelease #NewFeatures
 - Focus on driving engagement and clicks
 - Ensure all links and hashtags are included
 
-[RULES]
+[RULES]

templates/release_notes_prompt.md

@@ -1,4 +1,9 @@
+## Summary of Changes
+
 [SUMMARY]
+
+## Instructions
+
 Write one comprehensive release notes document [PROJECT_TITLE] [VERSION] from the provided change summaries, following these guidelines:
 
 1. Structure  
@@ -34,4 +39,4 @@ Write one comprehensive release notes document [PROJECT_TITLE] [VERSION] from th
 
 [EXAMPLE]
 [RULES]
-Output only the final release notes—no extra commentary.
+

templates/summary_prompt.md

@@ -59,4 +59,4 @@ Write a structured, Keep a Changelog–style summary of the provided git diff. D
 
 [EXAMPLE]
 [RULES]
-Output only the completed summary—no additional commentary.
+

tests/replace_tokens.bats

@@ -138,6 +138,8 @@ Summary:
 Line A
 Line B
 Done.
+
+Output just the final content—no extra commentary or code fencing. Use only information contained in this prompt and the summaries provided above.
 EOF
 }
 
@@ -180,5 +182,7 @@ Rules:
 1. First rule
 2. Second rule
 
+
+Output just the final content—no extra commentary or code fencing. Use only information contained in this prompt and the summaries provided above.
 EOF
 }