Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
Deep codebase exploration using grepai semantic search and call graph tracing. Use this agent for understanding code architecture, finding implementations by intent, analyzing function relationships, and exploring unfamiliar code areas.
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
Delegate to this agent for deep codebase exploration — semantic search, exact symbol lookup and reference tracing over a Beacon index. Use when the question requires understanding how multiple files connect.
Read-only deep-dive of ONE repository inside a workspace fan-out task. Receives the user task + projectpath + seed chunks (with the main agent's commentary on what to trust and what to question) + an explicit deliverable. Returns whatever the main agent asked for, in the format they asked for. Use only when the main…
Delegated, token-isolated code LOCATOR for C/C++ (clangd), C#/.NET (Roslyn), JS/TS (tsserver), and Python (pyright) projects — no IDE needed. It LOCATES (symbols / references / definitions / files) via the official language-server index and returns ONLY a compact file:line table; it never reads or returns bodies.…
Delegated, token-isolated game-engine/build/structured log analysis. Hand it a log path (Unreal Saved/Logs, Unity Editor.log, Godot output, MSVC/UBT/MSBuild build output, or any .log/.jsonl) plus a question — "what errors", "what's flooding it", "what changed since last run", "track this scalar over time", "which…
A separate agent for reviewing complex codebase decisions, large refactors, and difficult cause analysis. A refactor changes internal code structure while aiming to preserve behaviour.
A separate agent for researching an existing codebase, including its patterns, affected areas, and similar implementations. It reports evidence from specific files, functions, and lines without changing files.
A separate agent that reviews security-sensitive code changes without editing files or reading sensitive configuration. It focuses on authentication, permissions, payments, deletion, and handling of outside input.
Your default search for all code search queries via Miru MCP — best, fastest, and cheapest. Use search, expand, and findrelated instead of grepsearch or codebasesearch when Miru is connected.
Fast code search agent that uses indexed search (qgrep) for large codebases. Spawn this agent when exploring, searching, or investigating code across a repository — especially repos with 5k+ files where standard grep is slow.
Use this skill before answering questions about a repository's architecture, implementation locations, symbols, references, dependencies, refactoring impact, data flow, bugs, or where something is implemented. It searches a local hybrid codebase index so Claude reads only the most relevant files instead of scanning…
Use BEFORE writing code for a feature or a new project — this is the design gate that prevents hallucinated work. It (1) grounds itself in the project's REAL standards (CLAUDE.md + Cerebro), (2) asks you in detail what functionality to include/design, and (3) returns a grounded spec/plan to approve. It does NOT write…
Use to ANSWER questions about an existing codebase — "where is X?", "how does Y work?", "what depends on Z?", "explain this module or flow" — WITHOUT spending tokens re-reading folders. Read-only navigator that queries the Cerebro brain first and only opens files when the brain has no/stale info. Use PROACTIVELY…