What problem does it solve? Reverse-engineering a legacy codebase requires deep, module-by-module analysis that is tedious and error-prone when done manually. This Skill automates the excavation phase of a reverse engineering workflow, extracting control flows, algorithms, data structures, and business rules from legacy code into structured documentation. ## Core Features & Use Cases - Module-by-module code analysis: Extracts functions, control flow, non-trivial algorithms, validation logic, and error handling from each module defined in the analysis plan. - Data dictionary generation: Documents entities, fields, types, required values, and relationships, with output depth controlled by a configurable doc_level (essencial, completo, detalhado). - Mermaid flowcharts and structured JSON: Produces per-module flowcharts and a modules.json file following a defined schema, with confidence levels (confirmed, inferred, unknown) for every finding. - Checkpointed sessions: Saves progress per module in state.json and offers preventive pauses after intensive analysis so work can resume in a fresh session. - Use Case: After running the reversa-scout on an undocumented legacy system, invoke this Skill to excavate each module and produce code-analysis.md, data-dictionary.md, and flowcharts that downstream agents use to write specifications. ## Quick Start Run the reversa-archaeologist after the scout phase to analyze each planned module of my legacy project and generate the code analysis, data dictionary, and flowcharts.
