What problem does it solve? Reverse-engineering a legacy codebase requires deep, module-by-module analysis that is easy to lose track of across long sessions. This Skill performs the excavation phase of a reverse engineering workflow, systematically extracting control flows, algorithms, data structures, and business rules from legacy code into structured, reusable documentation. ## Core Features & Use Cases - Module-by-module deep analysis: Extracts functions, conditionals, loops, error handling, algorithms, validation logic, entities, DTOs, constants, and feature flags from each module in the analysis plan. - Tiered documentation output: Generates code-analysis.md, data-dictionary.md, and Mermaid flowcharts scaled to the configured doc_level (essencial, completo, detalhado). - Checkpointed sessions: Saves per-module checkpoints to .reversa/state.json and offers preventive pauses after intensive analysis so work can resume in a fresh session without quality loss. - Use Case: After running the reversa-scout on an unfamiliar legacy system, use this Skill to produce a structured modules.json (per the references schema) plus human-readable analysis that downstream agents (Detective, Architect, Writer) consume. ## Quick Start Analyze the legacy project modules listed in .reversa/plan.md and generate the code analysis, data dictionary, and flowcharts into the output folder defined in .reversa/state.json.
