system-mapping

What problem does it solve?

It prevents change blindness by helping you quickly understand architecture, execution flow, observability, dependencies, and runtime configuration before making code changes.

Core Features & Use Cases

• 5-point pre-flight checklist: architecture mapping, execution flow tracing, logging inventory, dependency analysis, and environment scan.
• Decision-tree guidance: tells you when to skip, when to partially map, and when to do full mapping based on change size and familiarity.
• Index- and AST-aware discovery: uses structured index data when available and structural/code-search approaches when not, to find entry points, call chains, imports, and configuration signals.
• Use case: before editing an unfamiliar module or touching multiple files, generate a focused map of what you’ll affect and what you’ll need to observe during verification.

Quick Start

Use system-mapping before starting any unfamiliar or multi-file code change to produce a concise “what/where/how/depends/config” readiness summary for the work.