get_module_context
Analyze a module's complete structure, dependencies, and functionality before making changes or writing documentation to prevent breaking existing systems.
Instructions
Get everything you need to know about a module BEFORE modifying it or writing a PRD.
CALL THIS WHEN: • You're about to change code in a module — understand its full surface area first • You're writing a PRD or design doc and need ground-truth about what exists • You need to know what depends on this module (who breaks if you change it) • You want to see a module's DB tables, endpoints, cron jobs, or env vars at a glance
RETURNS: Complete module profile in ~2K tokens: file count, LOC, all exported function signatures with complexity, dependency graph (imports from + imported by), DB table access, HTTP endpoints, cron jobs, env vars, vision spec alignment, and external callers from other modules.
EXAMPLES: • "What does the slack module look like before I add a new notification?" • "What endpoints does the auth module expose?" • "Which modules depend on the db module?" • "What env vars does the crons module use?"
WHY NOT JUST READ FILES: A module can span dozens of files. Manual exploration burns 10K-40K tokens and still misses cross-module callers, DB access patterns, and vision spec alignment. This returns the complete picture in one call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||