reversa-data-master

Documents legacy database schemas, relationships, and business rules into Mermaid ERDs and Markdown artifacts.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-data-master-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-data-master
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-data-master
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-data-master-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legacy projects often lack up-to-date database documentation, making reverse engineering, onboarding, and modernization risky and slow. This Skill analyzes whatever database evidence is available and produces a complete, structured documentation set. ## Core Features & Use Cases - Full schema inventory: Catalogs tables, columns, types, keys, indexes, and constraints, grouped by business domain. - Relationship and ERD generation: Maps cardinalities (1:1, 1:N, N:M), junction tables, and polymorphic relations, then renders Mermaid erDiagram output, including partial ERDs per domain for large databases. - Business rule extraction: Documents triggers, stored procedures, functions, views, and check constraints, with a confidence scale (direct DDL, inferred from ORM, or inaccessible). - Use Case: Given a legacy Laravel app with migrations and Eloquent models, generate erd.md, data-dictionary.md, relationships.md, business-rules.md, and procedures.md under the output folder for a reverse-engineering specification. ## Quick Start Ask the agent to document the legacy project's database by analyzing the available DDL files, migrations, or ORM models and generating the ERD and data dictionary.

Frequently Asked Questions about reversa-data-master

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

FAQPage Schema
How do I document a legacy database without existing documentation?▼

Point the Skill at whatever evidence exists: DDL files, migrations, ORM models, or screenshots of database tools. It inventories tables, maps relationships, and generates a data dictionary, ERD, and business rules documentation.

How to generate an ERD from migrations or ORM models?▼

The Skill parses migrations (Laravel, Rails, Flyway, Alembic, Prisma) or ORM models (Eloquent, ActiveRecord, SQLAlchemy, TypeORM) to infer tables and cardinalities, then renders Mermaid erDiagram output, with partial ERDs per domain for large schemas.

Can it connect directly to a production database?▼

Yes, but strictly read-only. The Skill explicitly forbids executing INSERT, UPDATE, DELETE, or DROP statements, using direct connections only to inspect schema metadata.

What output files does the database documentation produce?▼

It writes erd.md, data-dictionary.md, relationships.md, business-rules.md, and procedures.md into the database/ subfolder of the configured output folder, defaulting to _reversa_sdd.

What are the limitations when only ORM models are available?▼

Structures inferred from ORM models or screenshots are marked with a medium confidence level, since database-level objects like triggers, views, and check constraints may not be visible in application code.