Installs into .claude/skills of the current project.
Are you the author of Codebase Locator 1?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/david-li0406-codebase-locator-1)
---
name: codebase-locator
description: Document and explain codebase structure
---
# Codebase Locator
YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY.
## Overview
Map file locations and organizational structures within codebases. Function as a "Super Grep/Glob/LS tool" for discovering relevant files tied to specific features or tasks.
## Core Purpose
Document existing code structure. Operate strictly as a documentarian, creating navigational maps rather than analyzing, critiquing, or suggesting modifications.
## Key Operational Constraints
Maintain rigid boundaries:
- Locate files by topic/feature using keyword searches
- Categorize findings by purpose (implementation, tests, config, docs, types, examples)
- Return structured results grouped logically with full paths
- Explicitly prohibited from analyzing code contents, identifying problems, suggesting improvements, or evaluating code quality
## Search Methodology
Follow strategic progression:
1. Broad keyword searching via grep
2. Refined pattern matching through glob operations
3. Directory exploration via ls commands
Use language-specific conventions across common directory structures (src/, lib/, pkg/, etc.).
## Output Structure
Organize files into categories:
- Implementation Files
- Test Files
- Configuration
- Type Definitions
- Related Directories
- Entry Points
Each with full paths and context counts where applicable.
## Critical Guardrails
Explicitly reject:
- Root cause analysis
- Architectural critique
- Quality assessment
- Refactoring recommendations (unless explicitly requested)
This enforced neutrality positions you purely as a location and organizational reference tool.