feat: register slash commands via config hook

- Add config hook to programmatically register /search, /find, /index commands
- Commands now auto-register when plugin loads (no manual copy needed)
- Update README with simplified local development instructions

Author: Helweg

README.md

@@ -155,12 +155,7 @@ Maintenance tool to remove stale entries from deleted files.
 
 ## 🎮 Slash Commands
 
-For easier access, you can add slash commands to your project.
-
-Copy the commands:
-```bash
-cp -r node_modules/opencode-codebase-index/commands/* .opencode/command/
-```
+The plugin automatically registers these slash commands:
 
 | Command | Description |
 | ------- | ----------- |
@@ -238,19 +233,16 @@ Be aware of these characteristics:
    npm run build
    ```
 
-2. **Deploy to OpenCode Cache**:
-   ```bash
-   # Deploy script
-   rm -rf ~/.cache/opencode/node_modules/opencode-codebase-index
-   mkdir -p ~/.cache/opencode/node_modules/opencode-codebase-index
-   cp -R dist native commands skill package.json ~/.cache/opencode/node_modules/opencode-codebase-index/
-   ```
-
-3. **Register in Test Project**:
-   ```bash
-   mkdir -p .opencode/plugin
-   echo 'export { default } from "$HOME/.cache/opencode/node_modules/opencode-codebase-index/dist/index.js"' > .opencode/plugin/codebase-index.ts
+2. **Register in Test Project** (use `file://` URL in `opencode.json`):
+   ```json
+   {
+     "plugin": [
+       "file:///path/to/opencode-codebase-index"
+     ]
+   }
    ```
+   
+   This loads directly from your source directory, so changes take effect after rebuilding.
 
 ## 🤝 Contributing
 

src/index.ts

@@ -52,6 +52,43 @@ const plugin: Plugin = async ({ directory }) => {
       index_status,
       index_health_check,
     },
+
+    async config(cfg) {
+      cfg.command = cfg.command ?? {};
+
+      cfg.command["search"] = {
+        description: "Search codebase by meaning using semantic search",
+        template: `Use the \`codebase_search\` tool to find code related to: $ARGUMENTS
+
+If the index doesn't exist yet, run \`index_codebase\` first.
+
+Return the most relevant results with file paths and line numbers.`,
+      };
+
+      cfg.command["find"] = {
+        description: "Find code using hybrid approach (semantic + grep)",
+        template: `Find code related to: $ARGUMENTS
+
+Strategy:
+1. First use \`codebase_search\` to find semantically related code
+2. From the results, identify specific function/class names
+3. Use grep to find all occurrences of those identifiers
+4. Combine findings into a comprehensive answer
+
+If the semantic index doesn't exist, run \`index_codebase\` first.`,
+      };
+
+      cfg.command["index"] = {
+        description: "Index the codebase for semantic search",
+        template: `Run the \`index_codebase\` tool to create or update the semantic search index.
+
+Show progress and final statistics including:
+- Number of files processed
+- Number of chunks indexed
+- Tokens used
+- Duration`,
+      };
+    },
   };
 };