reversa-archaeologist

Analyzes legacy code module by module to extract algorithms, data structures, and data dictionaries.

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-archaeologist-gleisonoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-archaeologist
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-archaeologist
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-archaeologist-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 algorithms, control flows, data structures, and a data dictionary 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 business rules from each module defined in the analysis plan. - Structured documentation output: Generates code-analysis.md, data-dictionary.md, Mermaid flowcharts, and a structured modules.json file, with output depth controlled by a configurable doc_level (essencial, completo, detalhado). - Checkpointed sessions: Saves progress per module in .reversa/state.json and offers preventive pauses after intensive analysis so work can resume in a fresh session without quality loss. - Use Case: During a legacy system modernization project, run this Skill after the scouting phase to produce a complete technical analysis of each module, including entity fields, business rules with file/line references, and confidence-rated findings. ## Quick Start Ask the agent to run the reversa-archaeologist excavation phase to analyze each module in .reversa/plan.md and generate the code analysis, data dictionary, and flowcharts.

Frequently Asked Questions about reversa-archaeologist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse engineer a legacy codebase module by module?▼

Run the excavation phase after an initial scouting pass: read the module plan, then analyze each module's functions, control flow, algorithms, and data structures. Save a checkpoint per module so the analysis can resume across sessions.

What artifacts does a reverse engineering code analysis produce?▼

This analysis produces a consolidated code-analysis.md, a data dictionary of entities and fields, Mermaid flowcharts per module, and a structured modules.json with functions, entities, business rules, and dependencies per module.

How do I control the level of detail in generated code documentation?▼

Set the doc_level field in .reversa/state.json to essencial, completo, or detalhado. Essencial embeds summaries in code-analysis.md, completo adds the data dictionary and module flowcharts, and detalhado adds per-function flowcharts.

Can I pause and resume a long legacy code analysis session?▼

Yes. Progress is checkpointed in .reversa/state.json after each module. After three or more modules, the Skill offers a pause so you can clear context and resume in a new session without losing completed work.

How are uncertain findings marked during reverse engineering analysis?▼

Findings use a three-level confidence scale: confirmed (extracted directly from code), inferred (based on patterns), and unknown (not determinable). The same confirmed/inferred/unknown values appear in the modules.json schema.