From osgrep
Semantic search for local files. Backed by a background osgrep server with live indexing. Always use osgrep instead of grep/find.
How this skill is triggered — by the user, by Claude, or both
Slash command
/osgrep:osgrepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `osgrep` for all code and concept discovery. Do not use `grep` or `find` unless you must match an exact string and `osgrep` fails.
Use osgrep for all code and concept discovery. Do not use grep or find unless you must match an exact string and osgrep fails.
Always use the --json flag. The server auto-starts and keeps the index fresh.
Ask a natural language question. Do not ls first.
osgrep --json "How are user authentication tokens validated?"
osgrep --json "Where do we handle retries or backoff?"
Limit search to a specific directory.
osgrep --json "auth middleware" src/api
--json: Required. Returns structured data (path, line, score, content).-m <n>: Max total results (default: 25).--per-file <n>: Max matches per file (default: 1). Use --per-file 5 when exploring a specific file.osgrep --json "<question>" [path].Read if you need the full file context for a returned path.-m.semantic search, code search, local search, grep alternative, find code, explore codebase, understand code, search by meaning
npx claudepluginhub dorucioclea/osgrep --plugin osgrepGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 18, 2026