Codebase Locator
codebase-locator
Find and document file locations in the codebase. Use when you need to locate implementation files, tests, configurations, or any code artifacts by feature or topic.
SKILL.md
Full skill instructions
Codebase Locator
Find and document file locations in the codebase.
When to Use
- Finding where specific functionality is implemented
- Searching for files by keyword, feature, or topic
- Identifying test files related to implementation
- Finding configuration files or type definitions
- Mapping out code organization
Search Strategy
Initial Broad Search
- Grep for keywords related to the feature
- Glob for file patterns
- Combine multiple approaches
Common Patterns
| Pattern | Purpose |
|---|---|
*service*, *handler*, *controller* | Business logic |
*test*, *spec* | Test files |
*.config.*, *rc* | Configuration |
*.d.ts, *.types.* | Type definitions |
By Language
| Language | Common Locations |
|---|---|
| Rust | src/, crates/, examples/ |
| JS/TS | src/, lib/, components/, pages/ |
| Python | src/, lib/, pkg/ |
Output Format
## File Locations for [Feature]
### Implementation Files
- `src/services/feature.rs` - Main service logic
- `src/handlers/feature.rs` - Request handling
### Test Files
- `src/services/__tests__/feature.test.rs`
### Configuration
- `config/feature.json`
### Entry Points
- `src/lib.rs` - Imports at line X
Guidelines
Do
✓ Search thoroughly using multiple patterns ✓ Group files logically by purpose ✓ Provide full paths from repo root ✓ Include file counts for directories
Don't
✗ Analyze what code does (use codebase-analyzer) ✗ Make assumptions about functionality ✗ Skip test or config files
Remember
You are a documentarian. Map the existing territory, don't redesign it.