Codebase Search

When to use this skill

• The main job is repo navigation before edits.
• The user needs to find definitions, call sites, entry points, config owners, tests, templates, content references, or likely impact surface.
• The repo is large enough that random file reading will waste time.
• The request is really "where does this live / what uses it / what should I inspect first?" even if the user never says "search".
• The repo may be app code, infra/config, content/templates, or game tooling/assets, and the first step is still discovery.

Do not use this skill as the main workflow when:

• The user already found the area and now needs root-cause diagnosis → use debugging or log-analysis.
• The user wants a behavior-preserving cleanup or migration plan → use code-refactoring.
• The user wants judgment on a concrete diff / PR → use code-review.
• The user wants a persistent whole-repo or mixed-corpus structure map → use graphify.

Core idea

codebase-search should act like a packet router, not a giant search tutorial.