Stats
Actions
Tags
From ogrep
Semantic code search - finds code by meaning, not just keywords. Use when: - User asks WHERE or HOW something is implemented ("where is X handled", "how does Y work") - You need to understand code behavior without knowing exact function names - Exploring unfamiliar codebases where you don't know the terminology yet - User asks a conceptual question about the codebase NOT for: exact string matching, known file paths, import lookups, or simple identifier searches — use grep/Glob for those.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ogrep:ogrepThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**YOU MUST dispatch the ogrep-search agent for any semantic code search.**
YOU MUST dispatch the ogrep-search agent for any semantic code search.
Announce: "Dispatching ogrep search agent to find [topic]."
Then use the Agent tool with subagent_type: "ogrep-search":
Agent tool:
description: "Search codebase for [topic]"
prompt: "Search for [specific query]. Focus on [what you're looking for - e.g., implementation details, architecture, data flow, error handling]."
subagent_type: "ogrep-search"
The agent will:
--summarize for a cheap file-level overviewSaves context vs. running ogrep commands directly in your conversation.
Use ogrep when:
Use grep/Glob instead when:
class ErrorHandler)Rule of thumb: If you'd need to guess multiple terms for grep, dispatch the ogrep agent.
You CAN run ogrep commands directly via Bash, but DON'T — it wastes your context window with raw JSON output. Always dispatch the agent instead.
Exception: ogrep index . for first-time indexing can be run directly if the agent reports no index exists.
npx claudepluginhub gplv2/ogrep-marketplace --plugin ogrepSearches 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.
Performs semantic searches on codebases using natural language queries to locate orchestration logic, definitions, and call flows, with snippets, scores, and trace/skeleton options.
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.