reversa-archaeologist

Reverse engineering legacy code involves analyzing modules to extract control flow, algorithms, and data structures. This process produces structured artifacts like code-analysis markdown files and module JSON contexts for clear specification documentation.

Generating a data dictionary from legacy code requires analyzing entities and DTOs module by module. By configuring the documentation level, you can extract field-level types and constraints to output a comprehensive domain-oriented data dictionary.

Documenting legacy code algorithms for downstream agents requires extracting business logic into structured formats. Module analysis produces deterministic artifacts like modules.json and code-analysis markdown, providing clear execution contexts for automated consumption.

Architecture discovery requires a defined plan of modules and execution context before analysis. A prior scout pass must define the module structure in a plan file and surface JSON to guide the deterministic excavation of the codebase.

You can generate flowcharts when reverse engineering a legacy codebase by setting the appropriate documentation level. The analysis process optionally produces Mermaid flowcharts alongside structured artifacts to visualize control flow and module logic.

Module-by-module code analysis limitations depend on the defined documentation level and prior scout pass accuracy. The process strictly follows the defined module plan and surface context, meaning unlisted modules or undefined execution contexts will not be excavated.