reversa-detective

Extract implicit business knowledge from legacy Git history, ADRs, and permission matrices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill extrai conhecimento de negócio implícito de projetos legados, incluindo regras de negócio, ADRs retroativos, máquinas de estado e matrizes de permissões, para apoiar a engenharia reversa e a interpretação de sistemas legados.

Core Features & Use Cases

  • Extração de regras de negócio implícitas a partir do histórico de commits, ADRs e artefatos de arquitetura.
  • Geração de documentação de domínio, estados e políticas de acesso (RBAC) a partir de artefatos existentes.
  • Aplicação em cenários de engenharia reversa para entender o comportamento do sistema e orientar a reengenharia.

Quick Start

Analise o repositório legado para extrair conhecimento de negócio implícito usando ADRs, estados e permissões.

Frequently Asked Questions about reversa-detective

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

FAQPage Schema
How do I extract implicit business logic from legacy codebases using Git history?

This Skill extracts implicit business logic from legacy codebases by mining Git history, ADRs, and architectural artifacts to map domain concepts and uncover hidden business rules across multi-module projects.

Can I generate documentation for state machines and RBAC policies from existing legacy projects?

Yes, you can generate documentation for state machines and RBAC policies by analyzing existing legacy artifacts to map state transitions and permission matrices into discoverable domain documentation.

What is the best way to reverse engineer implicit domain rules from ADRs and commit history?

The best way to reverse engineer implicit domain rules from ADRs and commit history is to analyze historical artifacts to retroactively reconstruct governance decisions and map them to current system behavior.

Does this approach work for reverse engineering multi-module codebases with hidden permission matrices?

Yes, this approach works for reverse engineering multi-module codebases by specifically targeting hidden permission matrices and state transitions to generate guidance for reengineering efforts.

When do I need to mine ADRs and state machines for reverse engineering legacy systems?

You need to mine ADRs and state machines for reverse engineering legacy systems when you must map undocumented state transitions, governance decisions, and RBAC policies to generate discoverable domain documentation.