get_codebase_map
Generate a comprehensive codebase architecture map showing modules, dependencies, frequently changed files, and API endpoints to understand structure before starting development tasks.
Instructions
Pharaoh is a codebase knowledge graph. Call this FIRST — get the full architecture instead of reading files one-by-one.
CALL THIS WHEN: • You're starting a new task and need to understand the codebase structure • You need to know which modules exist and how they relate to each other • You want to find the most actively changed files (likely where bugs live) • You need to see all API endpoints at a glance
RETURNS: All modules with file counts and LOC, dependency graph with weights and bidirectional warnings, hot files (most changed in last 90 days), and all HTTP endpoints with their handler files.
EXAMPLES: • "What modules does this codebase have?" • "How is the codebase structured?" • "Which files change the most?" • "Are there any circular dependencies between modules?"
WHY NOT JUST READ FILES: Manually reading directory trees and package.json files gives you file structure but not dependency relationships, change frequency, or endpoint mappings. This gives you the full architectural picture in one call instead of 20+ file reads.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||