context-learning

To understand an unfamiliar codebase, trace imports, call chains, and data flows to generate a context analysis report. This highlights entry points, module purposes, and side effects, providing a suggested reading order for quick impact assessment during onboarding.

Trace call chains and dependencies by recursively mapping internal imports to a 2-3 level depth. This distinguishes internal references from external dependencies, helping you assess impact and identify necessary changes before refactoring.

Yes, you can analyze a specific folder for code review preparation. Apply the analysis to a provided folder path to auto-detect the entry file and produce concise flow diagrams, data flow notes, and short module summaries.

The best way to map data flows and side effects is to trace imports and call chains, then output a clear flow diagram. This identifies external dependencies and highlights side effects for concise impact analysis.

Context analysis works for bug investigation by mapping internal module references and tracing data flows. It summarizes module purposes and lists side effects, reducing friction and time spent locating the source of bugs.

Auto-detect entry points by applying analysis to a folder path. The tool uses common heuristics and package.json, when present, to identify the entry file and generate a concise context analysis report.