reversa-archaeologist

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

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-archaeologist-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-archaeologist
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-archaeologist
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-archaeologist-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers and analysts dissect legacy software, revealing algorithms, control flow, data structures, and data dictionaries module by module to support reverse engineering and modernization efforts.

Core Features & Use Cases

  • Deep module-level code analysis to extract algorithms, control flows, and data dictionaries.
  • Generates structured metadata and checkpoints to track progress across modules.
  • Useful in reverse-engineering legacy systems, auditing code quality, and guiding modernization projects.

Quick Start

Start by loading the plan and context files, then run the Archaeologist to begin module-by-module analysis.

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 legacy code to extract algorithms and data dictionaries?

Reverse engineering legacy code to extract algorithms and data dictionaries is done by analyzing the codebase module by module. This approach generates structured metadata and tracks progress using checkpoints to reveal control flows and data structures.

How do I analyze large legacy systems module by module for modernization planning?

Analyzing large legacy systems module by module for modernization involves enforcing per-module planning and state handling. This generates standardized artifacts like code-analysis and modules.json files to guide the modernization effort.

What is the best way to audit code quality across multiple legacy modules?

Auditing code quality across multiple legacy modules is best handled through deep module-level analysis. This process extracts control flows and data structures while generating structured metadata to assess the codebase systematically.

Can I control the output detail when extracting data structures from a legacy codebase?

Controlling output detail when extracting data structures from a legacy codebase is supported through a configurable doc_level setting. This adjusts the depth of the generated code-analysis artifacts according to your project requirements.

Does this module analysis approach work for large legacy systems with multiple modules?

Module analysis is applicable to large legacy systems with multiple modules. It handles state via a dedicated checkpoint mechanism and generates standardized metadata to ensure consistent tracking across the entire codebase.

What artifacts are generated when performing a deep code analysis of legacy software?

Artifacts generated during deep code analysis of legacy software include standardized code-analysis files and modules.json. These outputs document the extracted algorithms, control flows, and data dictionaries for each analyzed module.