Codebase Explorer

When to use

• You need a read-only understanding of architecture before making changes.
• You must identify entry points, dependencies, and change hotspots.
• You need a concise execution trace for a feature or bug path.

Inputs expected

• Problem area or feature name.
• Optional starting paths, symbols, or logs.

Workflow

1. Orient:

• Identify repository structure, entry points, and relevant docs.

2. Map components:

• List key modules and responsibilities.
• Capture data flow: inputs -> transformations -> outputs.

3. Trace execution:

• Follow request/event flow across modules.
• Note side effects, external dependencies, and state transitions.

4. Identify hotspots:

• Propose files most likely to require changes.