reversa-detective

Extract implicit business rules and state machines from legacy Git repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in uncovering implicit business knowledge from legacy projects, identifying business rules, and understanding the system's 'why' during reverse engineering analysis.

Core Features & Use Cases

  • Legacy Knowledge Extraction: Identify implicit business rules, ADRs, state machines, and permission matrices from legacy code.
  • Git Analysis: Analyze commit history for business decisions and technical changes.
  • Document Generation: Generate documentation for domain, state machines, permissions, and ADRs.
  • Use Case: When analyzing a complex legacy system, use this Skill to extract the business logic and state transitions, aiding in understanding the system's architecture.

Quick Start

Run the reversa-detective skill with the 'analyze' command on your legacy project repository.

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 rules and state machines from a legacy project?

Analyzing Git commit history uncovers implicit business knowledge from legacy projects by tracking technical changes and past decisions. It reveals the system's underlying 'why' and identifies undocumented business rules.

Can I generate documentation for permission matrices and state machines from existing source code?

Reverse engineering legacy code requires access to the project source code and Git repository. The analysis extracts implicit business knowledge, state transitions, and permission matrices directly from the codebase.

How do I identify implicit ADRs in a legacy codebase?

To start extracting business knowledge, run the analyze command on your legacy project repository. This initiates the reverse engineering process to identify state machines, ADRs, and permission matrices.

What do I need to reverse engineer business knowledge from a legacy system?

Generating documentation for state machines and permission matrices from legacy projects captures implicit domain logic and ADRs. This produces readable artifacts detailing the system's architectural decisions and business rules.