What problem does it solve?
Navigating unfamiliar codebases, tracing function call relationships, and assessing the impact of code changes is extremely tedious using only grep and manual file reads. This Skill solves that by building a precise, LSP-powered symbol and call-graph map of your project that lets you navigate code by definition and relationship instead of blind text search.
Core Features & Use Cases
- LSP-Powered Code Mapping: Builds a cached JSON map of project symbols and call edges stored in the .codemap/ directory at the project root, supporting Python, Java, TypeScript, Kotlin, and Clojure projects via language-specific adapters.
- Targeted Querying: Answer specific questions like "Where is this function defined?", "What calls this function?", or "What breaks if I edit this line?" without rebuilding the entire map.
- Incremental Refresh: Only rebuilds symbols and edges for files changed since the last map build, saving time on large projects.
- Use Case: When planning to modify a core payment processing function, use this Skill to trace all callers of the function across the project to identify potential breaking changes before writing any code.
Quick Start
Use the code-map skill to generate a symbol and call-graph map of your current project to trace all code that calls the process_payment function before making edits to it.