techunter 0.1.9 → 0.1.10

package/dist/index.js

@@ -1637,19 +1637,19 @@ import open2 from "open";
 // src/tools/new-task/prompts.ts
 var GUIDE_FORMAT = `
 ## Guide format
-Write the guide in the same language as the task title. Use plain markdown, no code blocks. Be concise. Include exactly these sections:
+Detect the language from the task title and write everything \u2014 including section headings \u2014 in that same language. Use plain markdown, no code blocks. Be concise. Include exactly these four sections (translate the heading names accordingly):
 
-### \u4EFB\u52A1\u63CF\u8FF0
-Describe what needs to be done and why. Cover the background, the problem being solved, and the expected outcome. Be as detailed as needed to make the task clear.
+### Task Description
+Describe what needs to be done and why. Cover the background, the problem being solved, and the expected outcome.
 
-### \u6D89\u53CA\u6587\u4EF6
+### Files Involved
 List each file path with CREATE/MODIFY, and one sentence describing what changes.
 
-### \u8F93\u5165 / \u8F93\u51FA
+### Input / Output
 What the feature/fix receives as input and what it produces or affects.
 
-### \u9A8C\u6536\u6807\u51C6
-Checkbox list of only the most essential testable conditions. Maximum 3 items \u2014 include only what is strictly necessary to verify the task is done.
+### Acceptance Criteria
+Checkbox list of only the most essential testable conditions. Maximum 3 items.
 `.trim();
 
 // src/tools/new-task/guide-generator.ts
@@ -2015,18 +2015,18 @@ import ora8 from "ora";
 
 // src/tools/reject/prompts.ts
 var REJECTION_FORMAT = `
-Write the rejection comment in the same language as the conversation. Use markdown. Include:
+Detect the language from the reviewer feedback and write everything \u2014 including section headings \u2014 in that same language. Use markdown. Include exactly these four sections (translate the heading names accordingly):
 
-### \u274C \u6253\u56DE\u539F\u56E0 / Rejection Reason
+### \u274C Rejection Reason
 One paragraph: what was reviewed and what the main problem is.
 
-### \u{1F527} \u9700\u8981\u4FEE\u6539\u7684\u5185\u5BB9 / Required Changes
+### \u{1F527} Required Changes
 Numbered, specific, actionable items. Reference file names and function names.
 
-### \u2705 \u672A\u901A\u8FC7\u7684\u9A8C\u6536\u6807\u51C6 / Failed Acceptance Criteria
+### \u2705 Failed Acceptance Criteria
 Re-list each criterion that was NOT met, prefixed with \u274C.
 
-### \u{1F4CB} \u4E0B\u4E00\u6B65 / Next Steps
+### \u{1F4CB} Next Steps
 Clear instruction on what to fix and how to re-submit (via /submit).
 `.trim();
 
@@ -3100,7 +3100,7 @@ function printBanner(config) {
   console.log("    " + g("\u255A\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u255D"));
   console.log("");
   console.log(
-    "    " + chalk14.bold("Techunter") + chalk14.dim(` v${version}`) + chalk14.dim("  \xB7  ") + chalk14.cyan("GLM-5") + chalk14.dim(" \xB7 zai-org") + chalk14.dim("  \xB7  ") + chalk14.dim(`${owner}/${repo}`)
+    "    " + chalk14.bold("Techunter") + chalk14.dim(` v${version}`) + chalk14.dim("  \xB7  ") + chalk14.cyan(getModel(config)) + chalk14.dim("  \xB7  ") + chalk14.dim(`${owner}/${repo}`)
   );
   console.log("");
 }

package/dist/mcp.js

@@ -1341,19 +1341,19 @@ import open from "open";
 // src/tools/new-task/prompts.ts
 var GUIDE_FORMAT = `
 ## Guide format
-Write the guide in the same language as the task title. Use plain markdown, no code blocks. Be concise. Include exactly these sections:
+Detect the language from the task title and write everything \u2014 including section headings \u2014 in that same language. Use plain markdown, no code blocks. Be concise. Include exactly these four sections (translate the heading names accordingly):
 
-### \u4EFB\u52A1\u63CF\u8FF0
-Describe what needs to be done and why. Cover the background, the problem being solved, and the expected outcome. Be as detailed as needed to make the task clear.
+### Task Description
+Describe what needs to be done and why. Cover the background, the problem being solved, and the expected outcome.
 
-### \u6D89\u53CA\u6587\u4EF6
+### Files Involved
 List each file path with CREATE/MODIFY, and one sentence describing what changes.
 
-### \u8F93\u5165 / \u8F93\u51FA
+### Input / Output
 What the feature/fix receives as input and what it produces or affects.
 
-### \u9A8C\u6536\u6807\u51C6
-Checkbox list of only the most essential testable conditions. Maximum 3 items \u2014 include only what is strictly necessary to verify the task is done.
+### Acceptance Criteria
+Checkbox list of only the most essential testable conditions. Maximum 3 items.
 `.trim();
 
 // src/tools/new-task/guide-generator.ts
@@ -1719,18 +1719,18 @@ import ora7 from "ora";
 
 // src/tools/reject/prompts.ts
 var REJECTION_FORMAT = `
-Write the rejection comment in the same language as the conversation. Use markdown. Include:
+Detect the language from the reviewer feedback and write everything \u2014 including section headings \u2014 in that same language. Use markdown. Include exactly these four sections (translate the heading names accordingly):
 
-### \u274C \u6253\u56DE\u539F\u56E0 / Rejection Reason
+### \u274C Rejection Reason
 One paragraph: what was reviewed and what the main problem is.
 
-### \u{1F527} \u9700\u8981\u4FEE\u6539\u7684\u5185\u5BB9 / Required Changes
+### \u{1F527} Required Changes
 Numbered, specific, actionable items. Reference file names and function names.
 
-### \u2705 \u672A\u901A\u8FC7\u7684\u9A8C\u6536\u6807\u51C6 / Failed Acceptance Criteria
+### \u2705 Failed Acceptance Criteria
 Re-list each criterion that was NOT met, prefixed with \u274C.
 
-### \u{1F4CB} \u4E0B\u4E00\u6B65 / Next Steps
+### \u{1F4CB} Next Steps
 Clear instruction on what to fix and how to re-submit (via /submit).
 `.trim();
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "techunter",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "AI-powered task distribution CLI for development teams",
   "author": "Techunter Contributors",
   "license": "MIT",