reversa-archaeologist

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-archaeologist-maximoseo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-archaeologist
Source: https://github.com/maximoseo/github-repos-radar/tree/main/.agents/skills/reversa-archaeologist
Command: npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-archaeologist-maximoseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analisa profundamente o código de projetos legados módulo a módulo, extraindo algoritmos, fluxos de controle, estruturas de dados e dicionário de dados para facilitar a engenharia reversa.

Core Features & Use Cases

  • Toma uma visão detalhada de cada módulo, gerando artefatos técnicos como code-analysis.md, data-dictionary.md, e diagramas de fluxo correspondentes.
  • Facilita onboarding de novas equipes, fornecendo documentação estruturada e um mapeamento de dependências entre módulos.
  • Pode ser usado na fase de escavação de engenharia reversa para transformar código legado em documentação acionável.

Quick Start

Analise o código legado módulo a módulo para produzir artefatos estruturados com algoritmos, fluxos de controle e estruturas de dados.

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 legacy code and extract its underlying algorithms?▼

Reverse engineering legacy code is best handled by analyzing the codebase module by module to extract algorithms, control flows, data structures, and a data dictionary. This approach generates structured documentation including code-analysis.md and data-dictionary.md artifacts.

How do I generate documentation for a legacy codebase that has no existing architecture records?▼

Generating documentation for a legacy codebase requires deep code-analysis across each module to produce structured artifacts. This process outputs a comprehensive code-analysis.md, data-dictionary.md, flowcharts, and a modules.json file with clear metadata and checkpoints.

Can I use module analysis to map dependencies and control flows across an entire project?▼

Module analysis can map dependencies and control flows across a project by taking a detailed view of each individual module. It extracts the specific algorithms and data structures, documenting findings to provide a complete architectural overview and onboarding mapping.

Does this code-analysis approach work for onboarding new teams onto unfamiliar legacy code?▼

This code-analysis approach works well for onboarding new teams by providing structured documentation and a clear mapping of dependencies between modules. It turns legacy code into actionable technical artifacts like flowcharts and data dictionaries for new developers.

What specific artifacts are produced during a deep reverse-engineering excavation of legacy code?▼

A deep reverse-engineering excavation produces specific code-analysis artifacts including code-analysis.md, data-dictionary.md, flowcharts, and modules.json. These files contain extracted algorithms, control flows, and clear metadata checkpoints for the analyzed codebase.