codemini-cli 0.1.16 → 0.1.17

package/OPERATIONS.md

@@ -85,6 +85,7 @@ codemini config list
 codemini config set shell.default powershell
 codemini config set ui.language en
 codemini config set soul.preset professional
+codemini config set soul.preset pirate
 ```
 
 ```bash

package/README.md

@@ -28,6 +28,7 @@ It is designed for teams that want a coding assistant that feels practical, cont
 - Structured code tools for small models: `locate`, `open_target`, `edit_target`
 - More conservative `plan auto` acceptance checks with reviewer/tester goal checklists
 - Tone presets through `soul`, without changing plans or code behavior
+- Example soul presets include `professional`, `playful`, `anime`, `pirate`, `caveman`, and `ceo`
 - Sub-agents for planning, coding, review, and testing
 
 ### Quick Start
@@ -142,6 +143,7 @@ CodeMini CLI 是一个为小模型工作流优化过的代码助手 CLI，重点
 - 为小模型补了结构化代码工具：`locate`、`open_target`、`edit_target`
 - `plan auto` 会基于原始目标生成验收清单，并更保守地处理 reviewer/tester 结果
 - `soul` 只影响语气，不影响计划和代码行为
+- 可用的 `soul` 示例包括 `professional`、`playful`、`anime`、`pirate`、`caveman`、`ceo`
 - 支持 planner、coder、reviewer、tester 多角色 sub-agent
 
 ### 快速开始

package/package.json

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

package/skills/brainstorm/SKILL.md

@@ -4,41 +4,16 @@ description: Lightweight brainstorming skill for 30B-class models. Use when a fe
 version: 0.1.0
 ---
 
-Use this skill only after the controller has decided the task needs clarification or option comparison before coding.
+Use this skill only when the task needs clarification or option comparison before coding.
 
-Primary purpose:
-- ask one high-value question when a key constraint is missing
-- compare 2-3 short options when the goal is clear but the approach is not
-- stop at a clear decision point
-
-Rules:
-
-1. Ask one question at a time.
-Do not dump a long questionnaire. Pick the most important uncertainty and resolve it first.
-
-1a. If a key uncertainty remains, stop after one question.
-Do not ask multiple numbered questions in the same reply. Do not continue into options, decisions, code, or file edits until that question is answered.
-
-2. Stay concrete.
-Focus only on the uncertainty that blocks execution.
-
-3. Offer 2-3 approaches only when the key constraint is already clear.
-Keep each option short and focused on the main tradeoff.
-
-4. Keep the design small.
-Do not expand a simple task into a long design discussion.
-
-5. Confirm before implementation.
-If options were given, wait for the user to choose unless the user explicitly asks for a recommendation.
-
-6. No code before convergence.
-Do not write implementation code, pseudo-code, or file edits while the direction is still being chosen.
-
-7. Do not decide for the user when the request is still under-specified.
-If the user has not provided enough information to choose confidently, ask the next best question and wait.
-
-8. Do not inspect the repo unless existing project context is directly relevant.
-For greenfield brainstorming, stay in conversation mode first.
+Core rules:
+- ask one question at a time
+- if a key uncertainty remains, ask the next best question and stop
+- give 2-3 short options only when the blocking constraint is already clear
+- keep options concrete and focused on the main tradeoff
+- present any conclusion as a suggested decision, not a final choice for the user
+- stop at the decision point unless the user clearly asks to continue
+- do not write code, pseudo-code, file edits, or broad repo exploration while direction is still being chosen
 
 Output format:
 
@@ -67,20 +42,9 @@ Option 3 (optional):
 - pros:
 - cons:
 
-Decision:
-- chosen:
+Suggested decision:
+- recommended:
 - reason:
 
-After decision:
-- stop after the chosen direction unless the user clearly asks to continue into implementation
-
-Suggested flow:
-- Restate the task briefly
-- Choose one mode only: Question or Options
-- Stop at a clear decision point
-
-Avoid:
-- large ceremonies
-- repeating the full conversation
-- asking multiple independent questions in one turn
-- proposing implementation details before the problem is clear
+After suggested decision:
+- stop after the recommended direction unless the user clearly asks to continue into implementation

package/skills/superpowers-lite/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: superpowers-lite
-description: Concise workflow skill tuned for 30B-class models: search first, keep context tight, use sub-agents for narrow tasks, and verify before claiming success.
+description: Concise workflow skill tuned for 30B-class models: prefer structured code tools first, keep context tight, use sub-agents for narrow tasks, and verify before claiming success.
 version: 0.1.0
 ---
 
@@ -33,10 +33,17 @@ Routing:
 - ask one high-value question before coding
 - do not assume features, storage model, or scope unless the user already gave them
 
+Tool order:
+- prefer `locate` first for repo search and candidate discovery
+- use `open_target` to inspect the smallest useful code block with edit metadata
+- use `edit_target` for minimal validated edits
+- use `search_code`, `read_block`, and `read_symbol_context` when lower-level structured context is needed
+- use shell search such as `rg` only as a fallback when structured tools are not enough
+
 Core rules:
 
 1. Search first.
-Use `rg` for repo search before broad file reads. Prefer local context commands and read only the smallest useful slice.
+Prefer structured search before broad file reads. Start with `locate`, then inspect with `open_target`, and only fall back to shell search such as `rg` when the structured tools are not enough.
 
 2. Keep context tight.
 Do not carry full conversation history into every step. Summarize, narrow scope, and work from the most recent relevant evidence.
@@ -55,18 +62,18 @@ If the requested behavior, scope, or acceptance is unclear, do not jump into imp
 - clear enough to build -> proceed
 
 5. Read and write with intent.
-Use `read_file` only when shell output is not enough. Use `write_file` for edits. Avoid unnecessary tool calls and avoid rereading the same file without a reason.
+Use `open_target`, `read_block`, and `read_symbol_context` before `read_file` when possible. Use `edit_target` for focused edits. Use `write_file` only for full-file writes. Avoid unnecessary tool calls and avoid rereading the same file without a reason.
 
 6. Verify before claiming success.
 Run the relevant test, check, or command before saying work is fixed or complete.
 
 Default workflow:
-- Search with `rg`
-- Inspect local context
+- Search with `locate`
+- Inspect local context with `open_target`
 - If the request is unclear, first decide: ask one question, brainstorm, or proceed
 - Plan the next smallest step
 - Delegate if the work is independent
-- Edit
+- Edit with `edit_target`
 - Verify
 - Summarize briefly
 

package/souls/caveman.md

@@ -0,0 +1,3 @@
+Respond with a simple caveman-inspired tone.
+Keep sentences short, readable, and practical, while still preserving technical accuracy.
+Do not make the wording so primitive that instructions become unclear.

package/souls/ceo.md

@@ -0,0 +1,3 @@
+Respond with a bold CEO-style tone.
+Keep the answer concise, forward-moving, and focused on fundamentals, tradeoffs, and execution.
+Do not imitate any real person, and do not let the style override careful technical judgment.

package/souls/pirate.md

@@ -0,0 +1,3 @@
+Respond with a playful pirate-inspired tone.
+Keep the answer clear, useful, and technically accurate first, with light nautical flavor.
+Do not overdo slang, and do not let the roleplay reduce precision.

package/src/cli.js

@@ -4,7 +4,7 @@ import { handleConfig } from './commands/config.js';
 import { handleDoctor } from './commands/doctor.js';
 import { handleSkill } from './commands/skill.js';
 
-const VERSION = '0.1.16';
+const VERSION = '0.1.17';
 
 function printHelp() {
   console.log(`codemini ${VERSION}

package/src/core/chat-runtime.js

@@ -2545,7 +2545,7 @@ export async function createChatRuntime({
               'Explicit brainstorm mode:',
               '- Ask exactly one clarifying question first if any important uncertainty remains.',
               '- Do not inspect the repo or generate code unless the user explicitly asks for that.',
-              '- Do not choose an option on the first reply unless the request is already specific enough or the user explicitly asks you to recommend one.',
+              '- If you recommend an option, present it as a suggested decision rather than a final choice for the user.',
               parsedInput.args.length > 0 ? `Current question:\n${parsedInput.args.join(' ')}` : ''
             ]
               .filter(Boolean)

package/src/core/command-policy.js

@@ -16,13 +16,13 @@ function suggestionForToken(token, config) {
   const shell = String(config?.shell?.default || '').toLowerCase();
   if (token === 'find' || token === 'grep') {
     return shell === 'powershell'
-      ? 'Use allowed search and context commands such as Get-ChildItem, Select-String, Get-Content, or rg when available.'
-      : 'Use allowed search and context commands such as rg, find, grep, sed, cat, or ls.';
+      ? 'Prefer structured tools like locate and open_target first. If you need shell fallback, use allowed search and context commands such as Get-ChildItem, Select-String, Get-Content, or rg when available.'
+      : 'Prefer structured tools like locate and open_target first. If you need shell fallback, use allowed search and context commands such as rg, find, grep, sed, cat, or ls.';
   }
   if (shell === 'powershell') {
-    return 'Use allowed shell commands for search and local context such as Get-ChildItem, Get-Content, Select-String, or rg when available.';
+    return 'Prefer structured tools like locate, open_target, and edit_target first. If you need shell fallback, use allowed shell commands for search and local context such as Get-ChildItem, Get-Content, Select-String, or rg when available.';
   }
-  return 'Use allowed shell commands for search and local context such as rg, find, grep, sed, cat, or ls.';
+  return 'Prefer structured tools like locate, open_target, and edit_target first. If you need shell fallback, use allowed shell commands for search and local context such as rg, find, grep, sed, cat, or ls.';
 }
 
 export function evaluateCommandPolicy(command, config, workspaceRoot = process.cwd()) {