@eldrforge/ai-service 0.1.22 → 1.0.1

package/README.md

@@ -1250,3 +1250,5 @@ Apache-2.0
 ## Changelog
 
 See [RELEASE_NOTES.md](./RELEASE_NOTES.md) for version history and changes.
+
+<!-- Build: 2026-01-15 15:59:12 UTC -->

package/dist/index.js

@@ -1680,9 +1680,11 @@ function createGetFileModificationTimesTool() {
 async function runAgenticCommit(config) {
   const {
     changedFiles,
-    diffContent,
+    diffContent: _diffContent,
+    // Optional - AI can use tools to read files
     userDirection,
-    logContext,
+    logContext: _logContext,
+    // Optional - AI can use get_recent_commits tool
     model = "gpt-4o",
     maxIterations = 10,
     debug = false,
@@ -1700,14 +1702,8 @@ async function runAgenticCommit(config) {
   });
   const tools = createCommitTools();
   toolRegistry.registerAll(tools);
-  const toolGuidance = generateToolGuidance(tools, {
-    strategy: "adaptive",
-    includeExamples: true,
-    explainWhenToUse: true,
-    includeCategories: true
-  });
-  const systemPrompt = buildSystemPrompt$3(toolGuidance);
-  const userMessage = buildUserMessage$2(changedFiles, diffContent, userDirection, logContext);
+  const systemPrompt = buildSystemPrompt$3();
+  const userMessage = buildUserMessage$2(changedFiles, userDirection);
   const messages = [
     { role: "system", content: systemPrompt },
     { role: "user", content: userMessage }
@@ -1741,10 +1737,22 @@ async function runAgenticCommit(config) {
     toolMetrics: result.toolMetrics
   };
 }
-function buildSystemPrompt$3(toolGuidance) {
+function buildSystemPrompt$3() {
   return `You are a professional software engineer writing commit messages for your team.
 
-${toolGuidance}
+## Available Tools
+
+You have access to tools to investigate the changes:
+- \`get_file_content\` - Read file contents or diffs for specific files
+- \`get_file_modification_times\` - See when files were modified relative to each other
+- \`group_files_by_concern\` - Understand how files relate by type/purpose
+- \`get_recent_commits\` - Get recent commit history to avoid duplicates
+- \`get_file_history\` - Understand how code evolved
+- \`get_file_dependencies\` - Assess impact of changes
+- \`get_related_tests\` - Find related test files
+- \`search_codebase\` - Search for usage patterns
+
+Use these tools to investigate the changes rather than asking for information upfront.
 
 ## Your Task
 
@@ -1850,37 +1858,30 @@ Split 3:
 
 Output only the commit message and splits. No conversational remarks or follow-up offers.`;
 }
-function buildUserMessage$2(changedFiles, diffContent, userDirection, logContext) {
+function buildUserMessage$2(changedFiles, userDirection) {
   const fileCount = changedFiles.length;
   const manyFiles = fileCount >= 5;
   let message = `I have staged changes that need a commit message.
 
 Changed files (${fileCount}):
-${changedFiles.map((f) => `  - ${f}`).join("\n")}
-
-Diff:
-${diffContent}`;
+${changedFiles.map((f) => `  - ${f}`).join("\n")}`;
   if (userDirection) {
     message += `
 
 User direction: ${userDirection}`;
-  }
-  if (logContext) {
-    message += `
-
-Recent commit history for context:
-${logContext}`;
   }
   message += `
 
 ## Your Analysis Task
 
-${manyFiles ? `With ${fileCount} files changed, consider whether these represent multiple distinct changes that should be split into separate commits.
+${manyFiles ? `With ${fileCount} files changed, investigate whether these represent multiple distinct changes that should be split into separate commits.
 
-` : ""}Gather signals to understand the changes:
-1. Use \`get_file_modification_times\` to see when files were modified relative to each other
-2. Use \`group_files_by_concern\` to understand how files relate by type/purpose
-3. Cross-reference both signals - temporal proximity and logical relatedness - to determine the best commit structure
+` : ""}Use your tools to investigate the changes:
+1. Use \`get_file_content\` to read the actual changes in the files
+2. Use \`get_file_modification_times\` to see when files were modified relative to each other
+3. Use \`group_files_by_concern\` to understand how files relate by type/purpose
+4. Use \`get_recent_commits\` to check recent commit history and avoid duplicates
+5. Cross-reference temporal proximity and logical relatedness to determine the best commit structure
 
 Consider:
 - What distinct features, fixes, or improvements are included?
@@ -1889,8 +1890,7 @@ Consider:
 
 ${manyFiles ? "With many files, consider whether multiple focused commits would be clearer than one large commit." : "If changes represent multiple logical concerns, suggest splits."}
 
-If context information is provided, use it only if relevant to these specific changes.
-Don't force connections that don't exist - focus on what actually changed.`;
+Start by reading the file contents to understand what actually changed.`;
   return message;
 }
 function sanitizeFilePath(filePath) {
@@ -2596,11 +2596,14 @@ async function runAgenticRelease(config) {
   const {
     fromRef,
     toRef,
-    logContent,
-    diffContent,
+    logContent: _logContent,
+    // Optional - AI can use tools to get commit log
+    diffContent: _diffContent,
+    // Optional - AI can use tools to get diffs
     milestoneIssues,
     releaseFocus,
     userContext,
+    targetVersion,
     model = "gpt-4o",
     maxIterations = 30,
     debug = false,
@@ -2618,21 +2621,14 @@ async function runAgenticRelease(config) {
   });
   const tools = createReleaseTools();
   toolRegistry.registerAll(tools);
-  const toolGuidance = generateToolGuidance(tools, {
-    strategy: "adaptive",
-    includeExamples: true,
-    explainWhenToUse: true,
-    includeCategories: true
-  });
-  const systemPrompt = buildSystemPrompt$2(toolGuidance);
+  const systemPrompt = buildSystemPrompt$2();
   const userMessage = buildUserMessage$1({
     fromRef,
     toRef,
-    logContent,
-    diffContent,
     milestoneIssues,
     releaseFocus,
-    userContext
+    userContext,
+    targetVersion
   });
   const messages = [
     { role: "system", content: systemPrompt },
@@ -2666,10 +2662,26 @@ async function runAgenticRelease(config) {
     toolMetrics: result.toolMetrics
   };
 }
-function buildSystemPrompt$2(toolGuidance) {
+function buildSystemPrompt$2() {
   return `You are a professional software engineer writing release notes for your team and users.
 
-${toolGuidance}
+## Available Tools
+
+You have access to tools to investigate the release:
+- \`get_tag_history\` - Understand release patterns
+- \`get_release_stats\` - Quantify scope of changes
+- \`compare_previous_release\` - See how this compares to previous releases
+- \`group_files_by_concern\` - Identify themes in changes
+- \`analyze_commit_patterns\` - Detect patterns in commits
+- \`get_file_content\` - Read file contents or diffs
+- \`analyze_diff_section\` - Expand unclear changes
+- \`get_file_history\` - Understand how code evolved
+- \`get_file_dependencies\` - Assess impact and reach
+- \`search_codebase\` - Find usage patterns
+- \`get_related_tests\` - Understand behavior changes
+- \`get_breaking_changes\` - Identify breaking changes (always use this)
+
+Use these tools to investigate the changes rather than asking for information upfront.
 
 ## Your Task
 
@@ -2731,25 +2743,26 @@ Structure your notes logically:
 
 ## Output Format
 
-When ready, format your response as JSON:
+When ready, output your release notes in this exact format:
 
-RELEASE_NOTES:
-{
-  "title": "Clear, factual title describing the main changes",
-  "body": "Detailed release notes in Markdown format"
-}
+RELEASE_TITLE:
+[A clear, factual title describing the main changes]
 
-Output only the JSON. No conversational remarks or follow-up offers.`;
+RELEASE_BODY:
+[Detailed release notes in Markdown format]
+
+Do not include any JSON, code blocks, or wrapper syntax. Output plain text and markdown only.
+No conversational remarks or follow-up offers.`;
 }
 function buildUserMessage$1(params) {
-  const { fromRef, toRef, logContent, diffContent, milestoneIssues, releaseFocus, userContext } = params;
-  let message = `I need comprehensive release notes for changes from ${fromRef} to ${toRef}.
-
-## Commit Log
-${logContent}
+  const { fromRef, toRef, milestoneIssues, releaseFocus, userContext, targetVersion } = params;
+  let message = `I need comprehensive release notes for changes from ${fromRef} to ${toRef}.`;
+  if (targetVersion) {
+    const versionNumber = targetVersion.replace(/^v/, "");
+    message += `
 
-## Diff Summary
-${diffContent}`;
+**CRITICAL VERSION INSTRUCTION: This is a release for version ${versionNumber}. You MUST use EXACTLY "${versionNumber}" in your release title. DO NOT use any development/prerelease version numbers you may see in the diff (like ${versionNumber}-dev.0 or similar). The release version is ${versionNumber}.**`;
+  }
   if (milestoneIssues) {
     message += `
 
@@ -2772,7 +2785,18 @@ ${userContext}`;
   }
   message += `
 
-Analyze these changes and write clear release notes. Consider:
+## Your Analysis Task
+
+Use your tools to investigate the changes between ${fromRef} and ${toRef}:
+1. Use \`get_release_stats\` to understand the scope of changes
+2. Use \`get_tag_history\` or \`compare_previous_release\` to see release patterns
+3. Use \`analyze_commit_patterns\` to detect themes
+4. Use \`group_files_by_concern\` to identify logical groupings
+5. Use \`get_breaking_changes\` to identify breaking changes (always check this)
+6. Use \`get_file_content\` or \`analyze_diff_section\` to understand specific changes
+7. Use \`get_file_dependencies\` and \`search_codebase\` to assess impact
+
+Write clear release notes that answer:
 - What's the main story of this release?
 - What problems does it solve?
 - What's the impact on users and developers?
@@ -2782,37 +2806,29 @@ If context information is provided, use it only if relevant to this specific pac
 Don't force connections that don't exist - if context describes changes in other packages
 or unrelated features, simply ignore it and focus on what actually changed in this release.
 
-Investigate as needed to write accurate, helpful release notes.`;
+Start by gathering statistics and understanding the scope, then investigate specific changes as needed.`;
   return message;
 }
 function parseAgenticResult(finalMessage) {
-  const jsonMatch = finalMessage.match(/RELEASE_NOTES:\s*\n([\s\S]*)/);
-  if (jsonMatch) {
-    try {
-      const jsonStr = jsonMatch[1].trim();
-      let parsed;
-      try {
-        parsed = JSON.parse(jsonStr);
-      } catch {
-        parsed = null;
-      }
-      if (parsed && parsed.title && parsed.body) {
-        return {
-          releaseNotes: {
-            title: parsed.title,
-            body: parsed.body
-          }
-        };
+  const titleMatch = finalMessage.match(/RELEASE_TITLE:\s*\n(.*?)(?=\n\nRELEASE_BODY:|\n\s*\nRELEASE_BODY:)/s);
+  const bodyMatch = finalMessage.match(/RELEASE_BODY:\s*\n([\s\S]*)/);
+  if (titleMatch && bodyMatch) {
+    const title2 = titleMatch[1].trim();
+    let body2 = bodyMatch[1].trim();
+    body2 = cleanJsonArtifacts(body2);
+    return {
+      releaseNotes: {
+        title: title2,
+        body: body2
       }
-    } catch {
-    }
+    };
   }
   const lines = finalMessage.split("\n");
   let title = "";
   let body = "";
   let inBody = false;
   for (const line of lines) {
-    if (!title && line.trim() && !line.startsWith("#")) {
+    if (!title && line.trim() && !line.startsWith("#") && !line.startsWith("RELEASE_")) {
       title = line.trim();
     } else if (title && line.trim()) {
       inBody = true;
@@ -2825,6 +2841,7 @@ function parseAgenticResult(finalMessage) {
     title = "Release Notes";
     body = finalMessage;
   }
+  body = cleanJsonArtifacts(body);
   return {
     releaseNotes: {
       title: title.trim(),
@@ -2832,6 +2849,15 @@ function parseAgenticResult(finalMessage) {
     }
   };
 }
+function cleanJsonArtifacts(text) {
+  text = text.replace(/^\s*\{\s*"title":\s*"[^"]*",?\s*"body":\s*"/m, "");
+  text = text.replace(/"\s*\}\s*$/m, "");
+  text = text.replace(/^```json\s*\n/gm, "");
+  text = text.replace(/^```\s*$/gm, "");
+  text = text.replace(/\\"/g, '"');
+  text = text.replace(/\\n/g, "\n");
+  return text.trim();
+}
 function createPublishTools() {
   return [
     createCheckGitStatusTool(),