codenavi

To map code flows in an unfamiliar codebase, you systematically investigate source directories to map dependencies and document structures. This process aids ongoing development tasks by logging discoveries into a persistent knowledge base.

Documenting code exploration findings involves maintaining a persistent `.notebook/` knowledge base. This approach retains investigation discoveries and detailed notes, ensuring knowledge is preserved for future development tasks.

Yes, you can use code analysis to fix bugs in undocumented source directories. By mapping relevant components and dependencies, the investigation process clarifies complex structures and produces detailed notes to guide your fixes.

To start investigating a specific component, specify the flow or component to analyze, then command the AI to investigate the source directory. The system will systematically review the code and update notes regarding that target.

Yes, code exploration requires systematic code review and note updating capabilities. This ensures accurate flow mapping and knowledge retention as you navigate complex, undocumented, or messy codebases during development.

You need to map dependencies and structures in code investigation when navigating complex, undocumented, or messy codebases. This systematic analysis clarifies workflows and aids in fixing bugs or implementing features efficiently.