jinn-map-codebase

To map an unfamiliar codebase for onboarding, identify the project entry points, trace dependencies outward to major subsystems, and document data movement to produce an architecture summary. This provides quick orientation for new contributors.

Tracing data flow across subsystems involves following dependencies outward from identified entry points to understand system boundaries. It requires documenting how data moves between modules and producing a summary of the architecture.

Architecture mapping helps when planning changes across modules by identifying entry points, major subsystems, and data paths. It produces an architecture summary that documents gaps, guiding developers on exactly where to start when making modifications.

Yes, you need to identify entry points before tracing dependencies. The process requires tracing outward from these entry points to major subsystems to understand system boundaries, data movement, and ultimately produce the architecture summary.

Yes, you can use this approach to find gaps in a codebase architecture. The process produces an architecture summary that explicitly documents entry points, subsystems, data flows, and identified gaps to guide onboarding and planning.