reversa-detective

Extract implicit business rules and architectural decisions from legacy codebases via Git history and static inspection.

Updated May 19, 2026
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-detective-silaslopes100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-detective
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-detective
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-detective-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of understanding undocumented legacy systems by extracting implicit business rules, state machines, and architectural decisions directly from the codebase and version history.

Core Features & Use Cases

  • Git Archaeology: Analyzes commit history to reconstruct ADRs and identify the evolution of business requirements.
  • Domain Mapping: Identifies business rules, state transitions, and permission structures hidden within the code.
  • Use Case: When taking over a project with no documentation, use this Skill to generate a comprehensive domain model and state machine diagrams to understand how the system actually behaves.

Quick Start

Run the reversa-detective skill to analyze the current repository and generate the full documentation suite in the output folder.

Frequently Asked Questions about reversa-detective

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

FAQPage Schema
How do I extract business logic and domain rules from legacy code?

To extract business logic from legacy code, analyze Git history and static code to identify implicit domain rules, state machines, and RBAC structures. This process reconstructs undocumented system behaviors into comprehensive engineering documentation.

What is Git archaeology for reverse engineering undocumented systems?

Git archaeology is the analysis of commit history to reverse engineer undocumented systems. It reconstructs Architecture Decision Records and tracks the evolution of business requirements, revealing why specific code structures were chosen over time.

How do I generate documentation for a project with no existing architectural records?

Generate documentation for undocumented projects by running static code inspection and Git history analysis. This produces a full documentation suite including domain models, state machine diagrams, and permission structures in the output folder.

Do I need a specific environment setup to perform static code inspection on legacy repositories?

Static code inspection of legacy repositories requires access to the repository root and a dedicated configuration directory. This environment setup allows systematic analysis to identify hidden domain rules and architectural decisions.

Can I identify RBAC structures and state machines hidden within legacy code?

Yes, you can identify RBAC structures and state machines hidden within legacy code through domain mapping. This technique extracts permission structures and state transitions directly from the codebase to build accurate domain models.

What are the limitations of reverse engineering legacy codebase architecture?

A limitation of reverse engineering legacy codebase architecture is the reliance on accessible Git history and readable static code. If commit history is sparse or code is heavily obfuscated, extracting implicit business rules becomes significantly harder.