reversa-archaeologist

Extract module-level control flow, algorithms, data structures, and domain rules from legacy codebases.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-archaeologist-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-archaeologist
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-archaeologist
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-archaeologist-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand and document a legacy codebase by extracting its real algorithms, control flow, data structures, and domain dictionary so you can safely plan refactors or migrations.

Core Features & Use Cases

  • Module-by-module code archaeology: Produces per-module control-flow analysis, algorithms, data structures, and business rules.
  • Data dictionary extraction: Generates a structured dictionary of fields and data relationships when configured for fuller documentation.
  • Cross-module synthesis artifacts: Always outputs consolidated code-analysis and structured modules context for downstream agents to use.
  • Engineering-reverse workflow support: Coordinates with the Reversa state/plan inputs and saves checkpoints to enable iterative excavation.

Quick Start

Use the reversa-archaeologist skill to analyze the modules listed in .reversa/plan.md, reading configuration from .reversa/state.json and writing outputs to the output_folder specified in the same state file.

Frequently Asked Questions about reversa-archaeologist

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

FAQPage Schema
How do I extract algorithms and control flow from a legacy codebase?

To extract algorithms and control flow from a legacy codebase, perform module-by-module reverse engineering to isolate per-module logic, data structures, and domain rules for safe refactoring or migration.

What is the best way to document data structures and domain rules for legacy modernization?

The best way to document data structures for legacy modernization is generating a structured data dictionary alongside consolidated code-analysis artifacts, capturing fields and data relationships to preserve domain logic.

Can I generate architecture documentation and flowcharts from existing source code?

Yes, you can generate architecture documentation and flowcharts from existing source code by applying deep reverse engineering to extract control flow and producing structured module context outputs.

How do I plan a staged excavation workflow for reverse engineering?

Plan a staged excavation workflow for reverse engineering by completing a scout phase first, then reading shared context and planned modules to iteratively analyze targeted code segments with checkpoint saving.

Does this code analysis approach require specific state inputs and configuration files?

Yes, this code analysis approach requires honoring `.reversa/state.json` settings and reading planned modules from `.reversa/plan.md` to correctly configure documentation levels and output folders.