From omo
Multi-strategy parallel search across the codebase. Combines symbol search, text patterns, file structure, imports, and git history for comprehensive results. Activate when #ds appears anywhere in the user message.
How this skill is triggered — by the user, by Claude, or both
Slash command
/omo:deep-searchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search the codebase for: $ARGUMENTS
Search the codebase for: $ARGUMENTS
Execute a multi-strategy parallel search to find code comprehensively.
Step 1 — Analyze the query:
Step 2 — Launch parallel searches (at least 3 strategies simultaneously):
git log for when code was added, modified, or deleted.Use deepsearch agent for parallel execution when the query is broad. Use direct Grep and Glob when the query is specific.
Step 3 — Synthesize results:
Step 4 — Provide actionable output:
End with:
Files (absolute path and relevance for each)Answer (direct answer to the actual need)ConfidenceAlternative queries (if confidence is not HIGH)npx claudepluginhub speson/omo --plugin omoSemantic 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.
Enhances codebase searches via semantic query parsing, regex patterns, AST analysis, symbol lookups, and optimized grep/ripgrep with relevance ranking and context.
Searches 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.