reversa-archaeologist

Analyze legacy codebases module by module to extract algorithms, control flows, and data structures.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-archaeologist-pabloprogramador23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-archaeologist
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa-archaeologist
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-archaeologist-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Archaeologist analyzes legacy codebases one module at a time, extracting algorithms, control flows, data structures, and a data dictionary to support reverse-engineering efforts.

Core Features & Use Cases

  • Module-by-module analysis: treats the codebase as a set of modules and documents each one's purpose, interactions, and key data models.
  • Algorithm and flow extraction: captures control flow, important conditional logic, loops, and non-trivial algorithms.
  • Artifacts produced: code-analysis.md and a structured modules.json describing entities, dependencies, and critical paths.

Quick Start

Run the archaeologist on the project to generate a complete module-by-module analysis.

Frequently Asked Questions about reversa-archaeologist

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

FAQPage Schema
What is the best way to reverse engineer a legacy codebase module by module?

Reverse engineering a legacy codebase module by module involves analyzing each module to extract algorithms, control flows, and data structures. This produces structured documentation and a data dictionary to support your reverse-engineering efforts.

How do I generate a data dictionary from legacy code?

To generate a data dictionary from legacy code, you deeply analyze the codebase module by module to extract data structures and entities. This produces a structured modules.json file that documents the critical paths and dependencies.

Can I use static analysis to extract control flow and algorithms from a monorepo?

Yes, static analysis can extract control flow and algorithms from a monorepo. By treating the project as a set of modules, it documents each module's purpose, important conditional logic, and non-trivial algorithms for reverse engineering.

How do I document legacy code architecture for reverse engineering?

Documenting legacy code architecture for reverse engineering requires analyzing module interactions and key data models. This generates a code-analysis.md file and a modules.json describing entities, dependencies, and critical paths.

What output artifacts are produced when analyzing a multi-module legacy system?

When analyzing a multi-module legacy system, the output artifacts produced are a code-analysis.md file and a structured modules.json. These files describe the extracted algorithms, entities, dependencies, and the data dictionary.