open-codebase-index 0.21.0-bootstrap.0

package/commands/search.md

@@ -0,0 +1,28 @@
+---
+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
+- `author=X` or `blameAuthor=X` → set blameAuthor filter
+- `sha=X` or `blameSha=X` → set blameSha filter
+- `since=YYYY-MM-DD` or `blameSince=YYYY-MM-DD` → set blameSince filter
+
+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"
+- `/search auth logic author=jane@example.com since=2025-01-01` → query="auth logic", blameAuthor="jane@example.com", blameSince="2025-01-01"
+
+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,19 @@
+---
+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
+- Failed embedding batches or compatibility warnings that explain why search is not ready
+
+No arguments needed - just run `index_status`.
+
+If not indexed:
+- suggest running `/index` when no index exists yet
+- if status reports failed embedding batches, tell the user to fix the provider/auth issue and rerun `/index` normally
+- if status reports provider/model incompatibility, tell the user to run `/index force` for a full rebuild

package/commands/visualize.md

@@ -0,0 +1,30 @@
+---
+description: Generate temporal HTML call graph visualization
+---
+
+Generate an interactive temporal call graph visualization that starts with recent movement/onboarding context, then supports module overview, symbol exploration, hotspots, and cycles.
+
+User input: $ARGUMENTS
+
+Parse input for optional parameters:
+- Plain text → directory filter (e.g., `/visualize src/services`)
+- `max=N` or "limit N" → sets maxNodes
+- `orphans` or `include-orphans` → sets includeOrphans=true
+- No input → visualize recent code movement plus entire call graph
+
+Call `index_visualize` with parsed parameters.
+
+Examples:
+- `/visualize` → temporal onboarding view with changes, modules, symbols, hotspots, and cycles
+- `/visualize src/tools` → only symbols in src/tools/
+- `/visualize max=1000` → limit to 1000 nodes
+- `/visualize src/indexer orphans` → include disconnected nodes
+
+If the index doesn't exist, run `index_codebase` first.
+
+Return the generated file path and open instructions.
+
+Terminology:
+- Modules are path-based code areas, such as `src/tools` or `native`.
+- Symbols are indexed named code units, such as functions, methods, classes, or Rust modules.
+- Cycles are loops where code can eventually call or depend back on itself.