fix(aidocs_classes): clarify recommendedNextVersionMessage field to require only the description body without the type(scope) prefix

changelog.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 2025-12-16 - 1.11.4 - fix(aidocs_classes)
+clarify recommendedNextVersionMessage field to require only the description body without the type(scope) prefix
+
+- Updated inline documentation in ts/aidocs_classes/commit.ts to explicitly state that recommendedNextVersionMessage must be only the description body (example: 'bump dependency to ^1.2.6') and not include the type(scope) prefix.
+- Removes ambiguity in the example text and improves guidance for commit message generation.
+
 ## 2025-12-15 - 1.11.0 - feat(commit)
 Integrate DualAgentOrchestrator for commit message generation and improve diff/context handling
 

ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@git.zone/tsdoc',
-  version: '1.11.0',
+  version: '1.11.4',
   description: 'A comprehensive TypeScript documentation tool that leverages AI to generate and enhance project documentation, including dynamic README creation, API docs via TypeDoc, and smart commit message generation.'
 }

ts/aidocs_classes/commit.ts

@@ -180,7 +180,7 @@ Here is the structure of the JSON you must return:
 {
   "recommendedNextVersionLevel": "fix" | "feat" | "BREAKING CHANGE",
   "recommendedNextVersionScope": "string",
-  "recommendedNextVersionMessage": "string",
+  "recommendedNextVersionMessage": "string (ONLY the description body WITHOUT the type(scope): prefix - e.g. 'bump dependency to ^1.2.6' NOT 'fix(deps): bump dependency to ^1.2.6')",
   "recommendedNextVersionDetails": ["string"],
   "recommendedNextVersion": "x.x.x"
 }