code-explorer

Trace code execution paths and map architecture using LSP tooling.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/aimskr/aims-claude-toolkit --skill code-explorer-aimskr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-explorer
Source: https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/code-explorer
Command: npx skills add https://github.com/aimskr/aims-claude-toolkit --skill code-explorer-aimskr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand unfamiliar codebases by tracing execution paths, mapping architecture layers, and navigating symbols with LSP support and a Grep fallback when needed.

Core Features & Use Cases

  • LSP-based symbol navigation: goToDefinition, findReferences, workspaceSymbol, and documentSymbol to locate and understand code.
  • Execution flow & architecture mapping: trace call graphs, data flow, and architectural boundaries to reveal feature implementations.
  • Dependency and reference analysis: identify inter-module dependencies and cross-file references to aid onboarding and refactoring.
  • Use Case: Onboard a new codebase by rapidly locating core components and their interactions, then document the architecture for future maintenance.

Quick Start

Install the LSP tools and run code-explorer from the project root to start tracing definitions, references, and architecture mappings.

Frequently Asked Questions about code-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace code execution paths and understand feature implementations in a large codebase?

To trace code execution paths in a large codebase, you can use LSP-based symbol navigation to map call graphs, locate definitions, and reveal architectural boundaries for feature implementations.

What is the best way to map architecture layers and dependencies for onboarding a new codebase?

The best way to map architecture layers and dependencies for onboarding is by analyzing inter-module dependencies and cross-file references to locate core components and document their interactions.

How does LSP tooling help with code analysis and reference tracing?

LSP tooling helps with code analysis by executing goToDefinition, findReferences, workspaceSymbol, and documentSymbol commands to precisely navigate symbols, trace data flow, and analyze references.

Can I use Grep-based search to find symbol references when LSP is unavailable?

Yes, you can use Grep-based search to find symbol references and navigate code when LSP tooling is unavailable, ensuring execution path tracing and dependency mapping remain functional.

Does code-explorer work for architectural reviews and dependency mapping in large projects?

Yes, code-explorer works for architectural reviews and dependency mapping in large projects by tracing cross-file references, mapping architectural boundaries, and identifying inter-module dependencies.

What do I need to install before using LSP for symbol navigation and code exploration?

You need to install the relevant LSP tools for your project and run code-explorer from the project root to start tracing definitions, references, and architecture mappings.