@khivi/opencode-codebase-index 0.5.2

package/commands/call-graph.md

@@ -0,0 +1,24 @@
+---
+description: Trace callers or callees using the call graph
+---
+
+Trace function dependencies using the `call_graph` tool.
+
+User input: $ARGUMENTS
+
+Interpret input as follows:
+- Default to `direction="callers"` unless input asks for callees/calls/makes calls.
+- `name=<function>` or plain text function name sets `name`.
+- `symbolId=<id>` is required for `direction="callees"`.
+
+Execution flow:
+1. If direction is `callers`, call `call_graph` with `{ name, direction: "callers" }`.
+2. If direction is `callees` and `symbolId` is present, call `call_graph` with `{ name, direction: "callees", symbolId }`.
+3. If direction is `callees` and `symbolId` is missing, first call `call_graph` with `direction="callers"` to get symbol IDs, then ask the user to choose one if multiple are returned.
+
+Examples:
+- `/call-graph Database` → callers for `Database`
+- `/call-graph callers name=Indexer` → callers for `Indexer`
+- `/call-graph callees name=Database symbolId=sym_abc123` → callees for selected symbol
+
+If output says no callers found, suggest running `/index force` first.

package/commands/find.md

@@ -0,0 +1,25 @@
+---
+description: Find code using hybrid approach (semantic + grep)
+---
+
+Find code using both semantic search and grep.
+
+User input: $ARGUMENTS
+
+Strategy:
+1. Use `codebase_search` to find semantically related code
+2. Identify specific function/class/variable names from results
+3. Use grep to find all occurrences of those identifiers
+4. Combine into a comprehensive answer
+
+Parse optional parameters from input:
+- `limit=N` → limit semantic results
+- `type=X` or "functions"/"classes" → filter chunk type
+- `dir=X` → filter directory
+
+Examples:
+- `/find error handling middleware`
+- `/find payment validation type=function`
+- `/find user auth in src/services`
+
+If no index exists, run `index_codebase` first.

package/commands/index.md

@@ -0,0 +1,21 @@
+---
+description: Index the codebase for semantic search
+---
+
+Run the `index_codebase` tool with these settings:
+
+User input: $ARGUMENTS
+
+Parse the input and set tool arguments:
+- force=true if input contains "force"
+- estimateOnly=true if input contains "estimate" 
+- verbose=true (always, for detailed output)
+
+Examples:
+- `/index` → force=false, estimateOnly=false, verbose=true
+- `/index force` → force=true, estimateOnly=false, verbose=true
+- `/index estimate` → force=false, estimateOnly=true, verbose=true
+
+IMPORTANT: You MUST pass the parsed arguments to `index_codebase`. Do not ignore them.
+
+Show final statistics including files processed, chunks indexed, tokens used, and duration.

package/commands/search.md

@@ -0,0 +1,24 @@
+---
+description: Search codebase by meaning using semantic search
+---
+
+Search the codebase using semantic search.
+
+User input: $ARGUMENTS
+
+The first part is the search query. Look for optional parameters:
+- `limit=N` or "top N" or "first N" → set limit
+- `type=X` or mentions "functions"/"classes"/"methods" → set chunkType
+- `dir=X` or "in folder X" → set directory filter
+- File extensions like ".ts", "typescript", ".py" → set fileType
+
+Call `codebase_search` with the parsed arguments.
+
+Examples:
+- `/search authentication logic` → query="authentication logic"
+- `/search error handling limit=5` → query="error handling", limit=5
+- `/search validation functions` → query="validation", chunkType="function"
+
+If the index doesn't exist, run `index_codebase` first.
+
+Return results with file paths and line numbers.

package/commands/status.md

@@ -0,0 +1,15 @@
+---
+description: Check if the codebase is indexed and ready for semantic search
+---
+
+Run the `index_status` tool to check if the codebase index is ready.
+
+This shows:
+- Whether the codebase is indexed
+- Number of indexed chunks
+- Embedding provider and model being used
+- Current git branch
+
+No arguments needed - just run `index_status`.
+
+If not indexed, suggest running `/index` to create the index.