@nomad-e/bluma-cli 0.1.30 → 0.1.32

package/dist/config/native_tools.json

@@ -40,7 +40,7 @@
       "type": "function",
       "function": {
         "name": "edit_tool",
-        "description": "Safely and precisely replaces text in a file, or creates a new file. The tool is resilient to common formatting issues but performs best with precise input.\n\n**Best Practices for Success:**\n1.  **Use a read tool first:** Always read the file to get the exact content before generating the `old_string`.\n2.  **Provide Context:** For `old_string`, provide a unique, multi-line segment of the file. Including 3+ lines of context around the target change is highly recommended to ensure precision.\n3.  **Create New Files:** To create a new file, provide the full `file_path` and an empty string for `old_string`.",
+        "description": "Replaces exact text in a file or creates a new file. Prefer **one** well-scoped edit over many tiny edits.\n\n**Critical — avoid line-by-line surgery:**\n- Do **not** change the same file in a dozen sequential calls with one line each; that drifts, breaks whitespace, and often fails.\n- After `read_file_lines`, copy a **single contiguous block** (whole function, whole component, or 5–20 lines with unique context) into `old_string`, then replace with your revised block in `new_string`.\n- If the tool reports no match or ambiguous match, **widen** `old_string` (more surrounding lines) or fix indentation to match the file **exactly** — do not blindly retry a one-line fragment.\n\n**CLI note:** The user may press Ctrl+O to see more lines of a **truncated** read/shell preview in the terminal. That view is UI-only and may still omit lines; always trust `read_file_lines` for exact text and whitespace before calling `edit_tool`.\n\n**Checklist:**\n1. Read the file first; use literal newlines in `old_string`/`new_string` (not the two-character sequence backslash-n).\n2. `expected_replacements` must match how many times `old_string` appears (default 1).\n3. New file: `old_string` empty, `new_string` full content.",
         "parameters": {
           "type": "object",
           "properties": {
@@ -560,7 +560,7 @@
           "properties": {
             "skill_name": {
               "type": "string",
-              "description": "Name of the skill to load. Examples: 'testing', 'git-conventional', 'docker', 'react'. Check available skills in the system prompt."
+              "description": "Exact skill name from the <available_skills> list in the system prompt (e.g. git-commit, git-pr, pdf). Do not invent names — use only names listed there."
             }
           },
           "required": [
@@ -573,29 +573,33 @@
       "type": "function",
       "function": {
         "name": "coding_memory",
-        "description": "Persists and retrieves short notes about the codebase, decisions, and context that should be remembered across turns. Use this to store important insights (APIs, invariants, design decisions) and to search them later.",
+        "description": "CRUD for durable coding notes on disk (~/.bluma/coding_memory.json), separate from chat. There is **no** action to wipe all entries: delete only one id at a time with `remove`.",
         "parameters": {
           "type": "object",
           "properties": {
             "action": {
               "type": "string",
-              "description": "Operation to perform: add a new note, list all notes, search by text/tags, or clear all entries.",
-              "enum": ["add", "list", "search", "clear"]
+              "description": "add=new note | list=all entries with ids | search=filter by query | remove=delete one entry by id | update=change note and/or tags for one id",
+              "enum": ["add", "list", "search", "remove", "update"]
+            },
+            "id": {
+              "type": "integer",
+              "description": "Required for remove and update. Obtain from list, search, or the id shown in the system prompt snapshot."
             },
             "note": {
               "type": "string",
-              "description": "The note to store when action is 'add'. Should summarize something worth remembering about the code, architecture, or requirements."
+              "description": "For add: full note text. For update: new note text (non-empty); omit if only changing tags."
             },
             "tags": {
               "type": "array",
               "items": {
                 "type": "string"
               },
-              "description": "Optional tags to categorize the note (e.g. ['api', 'auth', 'performance'])."
+              "description": "For add: optional tags. For update: optional new tag list (replaces tags when provided)."
             },
             "query": {
               "type": "string",
-              "description": "Search text used when action is 'search'. Matches against note text and tags."
+              "description": "Required for search. Matches note text and tags."
             }
           },
           "required": ["action"]