kfc-code-cli 0.0.1-alpha.2 → 0.0.1-alpha.21

package/README.md

@@ -3,7 +3,7 @@
 ## Install
 
 ```bash
-npm i -g kfc-code-cli@0.0.1-alpha.2
+npm i -g kfc-code-cli@alpha
 ```
 
 ## Usage

package/agents/default/agent.yaml

@@ -15,6 +15,7 @@ tools:
   - ReadMediaFile
   - SetTodoList
   - WebSearch
+  - Agent
   - FetchURL
   - AskUserQuestion
   - EnterPlanMode

package/agents/default/explore.yaml

@@ -13,7 +13,7 @@ promptVars:
     - Running read-only shell commands (git log, git diff, ls, find, etc.)
 
     Guidelines:
-    - Use Glob for broad file pattern matching
+    - Use Glob for broad file pattern matching. Patterns MUST contain a literal anchor (extension or subdirectory); pure wildcards like `*` or `**/*` are rejected by the tool.
     - Use Grep for searching file contents with regex
     - Use Read when you know the specific file path
     - Use Bash ONLY for read-only operations (ls, git status, git log, git diff, find)

package/agents/default/system.md

@@ -40,6 +40,7 @@ Always use tools to implement your code changes:
 When working on an existing codebase, you should:
 
 - Understand the codebase by reading it with tools (`Read`, `Glob`, `Grep`) before making changes. Identify the ultimate goal and the most important criteria to achieve the goal.
+- When using `Glob`, include a literal anchor (file extension or subdirectory) in the pattern. Pure wildcards like `*` or `**/*` are rejected by the tool.
 - For a bug fix, you typically need to check error logs or failed tests, scan over the codebase to find the root cause, and figure out a fix. If user mentioned any failed tests, you should make sure they pass after the changes.
 - For a feature, you typically need to design the architecture, and write the code in a modular and maintainable way, with minimal intrusions to existing code. Add new tests if the project already has tests.
 - For a code refactoring, you typically need to update all the places that call the code you are refactoring if the interface changes. DO NOT change any existing logic especially in tests, focus only on fixing any errors caused by the interface changes.