codemini-cli 0.5.9 → 0.5.11

package/deployment.md

@@ -1,212 +1,212 @@
-# Deployment Guide
-
-This document describes how to package, copy, install, configure, and verify `codemini-cli` from a `.tgz` file.
-
-## 1. Build The TGZ Package
-
-Run this in the project root on the packaging machine:
-
-```bash
-npm pack
-```
-
-Expected output:
-
-```text
-codemini-cli-0.5.5.tgz
-```
-
-If you want to verify the package contents:
-
-```bash
-tar -tf codemini-cli-0.5.5.tgz
-```
-
-## 2. Copy To The Target Machine
-
-Copy the generated `.tgz` file to the Win10 machine by one of these methods:
-
-- company internal file share
-- USB drive
-- secure artifact repository
-- SCP or similar internal transfer tool
-
-Recommended target path:
-
-```powershell
-C:\temp\codemini-cli-0.5.5.tgz
-```
-
-## 3. Environment Requirements
-
-Target machine requirements:
-
-- Windows 10
-- Node.js 22 or newer
-- npm available
-- PowerShell available
-
-Check:
-
-```powershell
-node -v
-npm -v
-```
-
-## 4. Install From TGZ
-
-Global install:
-
-```powershell
-npm install -g C:\temp\codemini-cli-0.5.5.tgz
-```
-
-If global install is blocked by company policy, install in a working directory instead:
-
-```powershell
-mkdir C:\temp\coder-test
-cd C:\temp\coder-test
-npm install C:\temp\codemini-cli-0.5.5.tgz
-```
-
-## 5. Confirm Installation
-
-If installed globally:
-
-```powershell
-codemini --help
-```
-
-If installed locally without global bin exposure:
-
-```powershell
-npx codemini --help
-```
-
-Or:
-
-```powershell
-node .\node_modules\codemini-cli\bin\coder.js --help
-```
-
-## 6. Initial Configuration
-
-Set your internal gateway, key, model, and shell:
-
-```powershell
-codemini config set gateway.base_url https://your-internal-gateway/v1
-codemini config set gateway.api_key your_token
-codemini config set model.name your_model_id
-codemini config set model.max_context_tokens 32768
-codemini config set shell.default powershell
-```
-
-Optional but recommended:
-
-```powershell
-codemini config set gateway.timeout_ms 180000
-codemini config set gateway.max_retries 2
-```
-
-Check current config:
-
-```powershell
-codemini config list
-```
-
-## 7. Smoke Test
-
-Run the built-in environment check:
-
-```powershell
-codemini doctor
-```
-
-Then launch the TUI:
-
-```powershell
-codemini
-```
-
-Inside the TUI, test these:
-
-```text
-/config list
-/history list
-/spec 写一个Win10内部CLI权限规范
-/plan from-spec
-帮我创建一个 hello.js
-读取 hello.js
-```
-
-## 8. Installed Data Locations
-
-Project-scoped data:
-
-```text
-.coder\
-```
-
-Global user/tool data on Win10:
-
-```text
-%APPDATA%\codemini-cli\
-```
-
-Typical contents:
-
-- `config.json`
-- `sessions\`
-- `skills\`
-- project skills are stored per workspace under `.codemini\skills\`
-- `input-history.json`
-
-## 9. Skills
-
-List installed skills:
-
-```powershell
-codemini skill list
-```
-
-Install a local skill into the current project:
-
-```powershell
-codemini skill install C:\path\to\skill-folder
-```
-
-Install a local skill globally:
-
-```powershell
-codemini skill install --scope=global C:\path\to\skill-folder
-```
-
-Rebuild the global registry:
-
-```powershell
-codemini skill reindex
-```
-
-## 10. Uninstall
-
-Global uninstall:
-
-```powershell
-npm uninstall -g codemini-cli
-```
-
-Local uninstall inside a test directory:
-
-```powershell
-npm uninstall codemini-cli
-```
-
-## 11. Known Limitation
-
-This `.tgz` package is suitable for package distribution, but it is not a fully self-contained offline dependency bundle.
-
-If the target machine is completely air-gapped and does not already have the required npm dependencies available, prepare one of these instead:
-
-- a tested `node_modules` bundle
-- a company internal npm mirror
-- a dedicated offline installer bundle
+# Deployment Guide
+
+This document describes how to package, copy, install, configure, and verify `codemini-cli` from a `.tgz` file.
+
+## 1. Build The TGZ Package
+
+Run this in the project root on the packaging machine:
+
+```bash
+npm pack
+```
+
+Expected output:
+
+```text
+codemini-cli-0.5.5.tgz
+```
+
+If you want to verify the package contents:
+
+```bash
+tar -tf codemini-cli-0.5.5.tgz
+```
+
+## 2. Copy To The Target Machine
+
+Copy the generated `.tgz` file to the Win10 machine by one of these methods:
+
+- company internal file share
+- USB drive
+- secure artifact repository
+- SCP or similar internal transfer tool
+
+Recommended target path:
+
+```powershell
+C:\temp\codemini-cli-0.5.5.tgz
+```
+
+## 3. Environment Requirements
+
+Target machine requirements:
+
+- Windows 10
+- Node.js 22 or newer
+- npm available
+- PowerShell available
+
+Check:
+
+```powershell
+node -v
+npm -v
+```
+
+## 4. Install From TGZ
+
+Global install:
+
+```powershell
+npm install -g C:\temp\codemini-cli-0.5.5.tgz
+```
+
+If global install is blocked by company policy, install in a working directory instead:
+
+```powershell
+mkdir C:\temp\coder-test
+cd C:\temp\coder-test
+npm install C:\temp\codemini-cli-0.5.5.tgz
+```
+
+## 5. Confirm Installation
+
+If installed globally:
+
+```powershell
+codemini --help
+```
+
+If installed locally without global bin exposure:
+
+```powershell
+npx codemini --help
+```
+
+Or:
+
+```powershell
+node .\node_modules\codemini-cli\bin\coder.js --help
+```
+
+## 6. Initial Configuration
+
+Set your internal gateway, key, model, and shell:
+
+```powershell
+codemini config set gateway.base_url https://your-internal-gateway/v1
+codemini config set gateway.api_key your_token
+codemini config set model.name your_model_id
+codemini config set model.max_context_tokens 32768
+codemini config set shell.default powershell
+```
+
+Optional but recommended:
+
+```powershell
+codemini config set gateway.timeout_ms 180000
+codemini config set gateway.max_retries 2
+```
+
+Check current config:
+
+```powershell
+codemini config list
+```
+
+## 7. Smoke Test
+
+Run the built-in environment check:
+
+```powershell
+codemini doctor
+```
+
+Then launch the TUI:
+
+```powershell
+codemini
+```
+
+Inside the TUI, test these:
+
+```text
+/config list
+/history list
+/spec 写一个Win10内部CLI权限规范
+/plan from-spec
+帮我创建一个 hello.js
+读取 hello.js
+```
+
+## 8. Installed Data Locations
+
+Project-scoped data:
+
+```text
+.coder\
+```
+
+Global user/tool data on Win10:
+
+```text
+%APPDATA%\codemini-cli\
+```
+
+Typical contents:
+
+- `config.json`
+- `sessions\`
+- `skills\`
+- project skills are stored per workspace under `.codemini\skills\`
+- `input-history.json`
+
+## 9. Skills
+
+List installed skills:
+
+```powershell
+codemini skill list
+```
+
+Install a local skill into the current project:
+
+```powershell
+codemini skill install C:\path\to\skill-folder
+```
+
+Install a local skill globally:
+
+```powershell
+codemini skill install --scope=global C:\path\to\skill-folder
+```
+
+Rebuild the global registry:
+
+```powershell
+codemini skill reindex
+```
+
+## 10. Uninstall
+
+Global uninstall:
+
+```powershell
+npm uninstall -g codemini-cli
+```
+
+Local uninstall inside a test directory:
+
+```powershell
+npm uninstall codemini-cli
+```
+
+## 11. Known Limitation
+
+This `.tgz` package is suitable for package distribution, but it is not a fully self-contained offline dependency bundle.
+
+If the target machine is completely air-gapped and does not already have the required npm dependencies available, prepare one of these instead:
+
+- a tested `node_modules` bundle
+- a company internal npm mirror
+- a dedicated offline installer bundle

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codemini-cli",
-  "version": "0.5.9",
+  "version": "0.5.11",
   "description": "Coding CLI optimized for small-model workflows and Windows PowerShell",
   "keywords": [
     "cli",

package/skills/brainstorm/SKILL.md

@@ -1,72 +1,77 @@
----
-name: brainstorm
-description: Lightweight brainstorming skill. Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.
-version: 0.2.0
----
-
-Use this skill only when the task needs clarification or option comparison before coding.
-
-**Announce:** When entering brainstorm, say "Using brainstorm to explore approaches before implementation."
-
-## Anti-Pattern
-
-Do NOT skip this skill for tasks that appear straightforward but lack clear requirements or constraints. Underspecified tasks cause the most wasted work. Even a few seconds of clarification beats a wrong implementation.
-
-## Process
-
-1. **Ask one question at a time.** If a key uncertainty remains, ask the next best question and STOP. Wait for the user's answer.
-2. **Give 2-3 short options** only when the blocking constraint is already clear. Keep options concrete and focused on the main tradeoff.
-3. **Present conclusions as suggested decisions**, not final choices.
-4. **Do NOT write code, pseudo-code, file edits, or broad repo exploration** while direction is still being chosen.
-
-## Output Formats
-
-### Mode A: key constraint missing
-
-```
-Question:
-- ask: <one specific question>
-- why this matters: <1-2 sentences on what this decides>
-```
-
-Wait for the user's answer. Do NOT proceed with options or code.
-
-### Mode B: goal is clear but approach choice remains
-
-```
-Option 1:
-- idea: <concrete approach>
-- pros: <1-2 points>
-- cons: <1-2 points>
-
-Option 2:
-- idea: <concrete approach>
-- pros: <1-2 points>
-- cons: <1-2 points>
-
-Option 3 (optional):
-- idea: <concrete approach>
-- pros: <1-2 points>
-- cons: <1-2 points>
-
-Suggested decision:
-- recommended: <option N>
-- reason: <why>
-```
-
-## Self-Review
-
-Before presenting options or a suggested decision, quickly check:
-
-- Are all options actually different, or are two of them the same idea in different words?
-- Does the recommended option match the user's stated constraints?
-- Did I invent requirements the user never mentioned? Remove them.
-
-## Exit
-
-After the user approves a direction:
-
-- If the task is small and clear enough to implement directly → proceed to code.
-- If the task is non-trivial or touches multiple areas → YOU MUST invoke `writing-plans` to create an implementation plan before coding.
-
-Do NOT stop at the brainstorm conclusion when the natural next step is planning.
+---
+name: brainstorm
+description: Lightweight brainstorming skill. Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.
+version: 0.2.1
+---
+
+Use this skill only when the task needs clarification or option comparison before coding.
+
+**Announce:** When entering brainstorm, say "Using brainstorm to explore approaches before implementation."
+
+## Anti-Pattern
+
+Do NOT skip this skill for tasks that appear straightforward but lack clear requirements or constraints. Underspecified tasks cause the most wasted work. Even a few seconds of clarification beats a wrong implementation.
+
+## Process
+
+1. **Ask one question at a time.** If a key uncertainty remains, ask the next best question and STOP. Wait for the user's answer.
+2. **Give 2-3 short options** only when the blocking constraint is already clear. Keep options concrete and focused on the main tradeoff.
+3. **Present conclusions as suggested decisions**, not final choices.
+4. **Do NOT write code, pseudo-code, file edits, or broad repo exploration** while direction is still being chosen.
+5. **Stop after your brainstorm response.** Do not say "I will start", "starting now", "I'll edit", or otherwise transition into implementation in the same turn.
+
+## Output Formats
+
+### Mode A: key constraint missing
+
+```
+Question:
+- ask: <one specific question>
+- why this matters: <1-2 sentences on what this decides>
+```
+
+Wait for the user's answer. Do NOT proceed with options or code.
+
+### Mode B: goal is clear but approach choice remains
+
+```
+Option 1:
+- idea: <concrete approach>
+- pros: <1-2 points>
+- cons: <1-2 points>
+
+Option 2:
+- idea: <concrete approach>
+- pros: <1-2 points>
+- cons: <1-2 points>
+
+Option 3 (optional):
+- idea: <concrete approach>
+- pros: <1-2 points>
+- cons: <1-2 points>
+
+Suggested decision:
+- recommended: <option N>
+- reason: <why>
+```
+
+After Mode B, STOP. Wait for the user to approve, reject, or revise the suggested decision.
+
+## Self-Review
+
+Before presenting options or a suggested decision, quickly check:
+
+- Are all options actually different, or are two of them the same idea in different words?
+- Does the recommended option match the user's stated constraints?
+- Did I invent requirements the user never mentioned? Remove them.
+
+## Exit
+
+Brainstorm ends only when the user sends a later message that clearly approves a direction, for example "use option 2", "按这个做", "确认，开始实现", or "直接写代码".
+
+After that later user approval:
+
+- If the task is small and clear enough to implement directly → proceed to code.
+- If the task is non-trivial or touches multiple areas → YOU MUST invoke `writing-plans` to create an implementation plan before coding.
+
+Do NOT treat your own suggested decision as approval. Do NOT continue from the brainstorm conclusion into planning or implementation until the user has explicitly approved a direction in a separate message.

package/skills/codemini.skills.json

@@ -1,40 +1,40 @@
-{
-  "version": 1,
-  "skills": {
-    "superpowers-lite": {
-      "description": "Default concise workflow for coding tasks; keep context tight, choose the right route, and verify before claiming success.",
-      "mode": "always",
-      "triggers": [],
-      "enabled": true,
-      "priority": 100
-    },
-    "brainstorm": {
-      "description": "Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.",
-      "mode": "agent_requested",
-      "triggers": [],
-      "enabled": true,
-      "priority": 70
-    },
-    "writing-plans": {
-      "description": "Use when you have a clear goal or approved design for a non-trivial task, before touching code.",
-      "mode": "agent_requested",
-      "triggers": [],
-      "enabled": true,
-      "priority": 75
-    },
-    "grill-me": {
-      "description": "Use when the user explicitly asks to pressure-test a plan, architecture choice, PR, launch, or product idea.",
-      "mode": "agent_requested",
-      "triggers": [],
-      "enabled": true,
-      "priority": 65
-    },
-    "project-requirements": {
-      "description": "Create a project requirements report with repository inspection and structured output artifacts.",
-      "mode": "manual",
-      "triggers": [],
-      "enabled": true,
-      "priority": 50
-    }
-  }
-}
+{
+  "version": 1,
+  "skills": {
+    "superpowers-lite": {
+      "description": "Default concise workflow for coding tasks; keep context tight, choose the right route, and verify before claiming success.",
+      "mode": "always",
+      "triggers": [],
+      "enabled": true,
+      "priority": 100
+    },
+    "brainstorm": {
+      "description": "Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.",
+      "mode": "agent_requested",
+      "triggers": [],
+      "enabled": true,
+      "priority": 70
+    },
+    "writing-plans": {
+      "description": "Use when you have a clear goal or approved design for a non-trivial task, before touching code.",
+      "mode": "agent_requested",
+      "triggers": [],
+      "enabled": true,
+      "priority": 75
+    },
+    "grill-me": {
+      "description": "Use when the user explicitly asks to pressure-test a plan, architecture choice, PR, launch, or product idea.",
+      "mode": "agent_requested",
+      "triggers": [],
+      "enabled": true,
+      "priority": 65
+    },
+    "project-requirements": {
+      "description": "Create a project requirements report with repository inspection and structured output artifacts.",
+      "mode": "manual",
+      "triggers": [],
+      "enabled": true,
+      "priority": 50
+    }
+  }
+}