code-investigator

Code investigation traces call chains from identified entry points to confirm specifications, providing evidence-based reports with precise file and line references. It distinguishes confirmed facts from unknowns and tracks runtime dependencies.

Bug investigation requires understanding current code behavior by systematically tracing execution paths. This approach identifies entry points, follows call chains, and generates reports with exact evidence, explicitly noting any uncertainties encountered during the trace.

Yes, visual flow documentation generates Mermaid diagrams for multi-file or complex workflows. This visualizes interactions traced during the code investigation, helping you understand intricate call chains and system behaviors.

You can save investigation findings to persistent memory storage. This stores the confirmed specifications and evidence-based reports in a searchable format, ensuring future reuse without needing to re-trace the same code paths.

Yes, uncertainty handling clearly distinguishes confirmed facts from unknowns and tracks runtime dependencies. When tracing code to verify behavior, it explicitly notes areas where specifications cannot be fully confirmed due to dynamic runtime conditions.

Evidence-based code investigation is limited by runtime dependencies and unknowns that cannot be statically traced. It explicitly notes these uncertainties in its reports, ensuring you understand which specifications are confirmed facts versus dynamic behaviors requiring runtime analysis.