This skill should be used when the user asks to understand code behavior, explore how something works, find where functionality is implemented, or asks questions like "how does X work", "where is Y handled", "what does Z do", "show me the code that", "find the implementation of", or "trace the flow of". Also use for exploring unfamiliar codebases or when grep/glob returns too many irrelevant results. Use BEFORE or ALONGSIDE keyword search.
How this skill is triggered — by the user, by Claude, or both
Slash command
/local-semantic-search:semantic-exploreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search code by meaning rather than keywords using semantic embeddings.
Search code by meaning rather than keywords using semantic embeddings.
Before searching, verify the codebase is indexed:
list_collections()
If the current working directory is not indexed:
index_codebase(directory="/absolute/path/to/project")
Use complete behavioral questions, not keywords:
semantic_search(
query="How does the system handle user authentication?",
collection="collection-name"
)
To get only file locations without code chunks:
semantic_search(
query="Where is authentication implemented?",
collection="collection-name",
include_code=False
)
Review top results by score (>0.7 = strong match). Use file paths and line numbers to read relevant code.
| Instead of | Use |
|---|---|
| "auth handler" | "How does the system authenticate users?" |
| "error" | "What happens when a request fails?" |
| "database" | "How does the application connect to and query the database?" |
| Semantic Search | Grep/Glob |
|---|---|
| "How does X work?" | Known symbol names |
| Behavior/intent questions | Specific strings |
| Exploring unfamiliar code | File patterns |
Match collection to current project:
list_collections() outputws-{hash} patternget_collection_info(collection) to verify point countServices must be running:
localhost:6333localhost:1335npx claudepluginhub adilasif/local-semantic-search-claude-code-plugin --plugin local-semantic-searchSearches codebases semantically with natural language queries to find implementations by concept (e.g., 'where is X', 'how does Y work'). Returns file paths, lines, and snippets.
Semantic codebase search — use for exploring code, finding implementations, and answering questions about any project. Searches using natural language queries, identifier names, or file paths. Returns ranked results using embedding-based similarity, BM25 keyword matching, symbol matching, import graph analysis, and git recency. Use this as the default exploration tool instead of grep when you don't know the exact text to search for.
Answers codebase questions by tracing flows and researching topics. Two modes: autonomous (structured output for subagents) and interactive (narrative with checkpoints).