codebase-locator

Document and explain codebase structure

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

The Codebase Locator is a specialized Claude skill designed to map, document, and explain the organizational structure of any software project. It functions as an advanced navigational assistant, utilizing strategic grep and glob operations to discover and categorize files—such as implementation logic, test suites, and configuration files—providing developers with a clear, structured map of their codebase for better accessibility and architectural understanding.

Use Cases

  • New Developer Onboarding: Rapidly orient new team members by providing a comprehensive map of the project's directory structure and key file locations.
  • Feature Discovery: Locate all files related to a specific feature or module by searching for relevant keywords across the entire repository.
  • Documentation Auditing: Generate a structured overview of implementation files, entry points, and type definitions to ensure project documentation matches the actual code structure.
  • Refactoring Preparation: Identify all related configuration and test files before starting a migration or refactoring task to ensure no dependencies are missed.
namecodebase-locator
descriptionDocument 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.