| name | explore |
| description | Use this skill when the user asks you something that requires searching a code base |
| metadata | {"author":"morph","version":"0.1.0","argument-hint":"<question>"} |
Explore
Use the codebase_search tool to explore a codebase, this saves time and tokens.
When To Use
- The user asks "how does this work?" or "where is X implemented?", anything that involves reading/tracing code
- You need entry points, data flow, or ownership of a behavior.
- Keyword grep is likely to miss the relevant files.
Steps
- Translate the user question into a tight natural language question, or description of the functionality you're looking for.
- Run 2-3 instances of the
codebase_search tool against the repo root, for each use a different search_string so you can explore the codebase from multiple angles
- Read the returned files/sections.
- Summarize the flow with concrete file paths.
Query Template
"Find the entry points and data flow for . Include router/handlers, config, and tests."