reversa-data-master

Document legacy database schemas, relationships, and business rules into structured Markdown artifacts.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-data-master-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-data-master
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-data-master
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-data-master-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legacy projects often lack up-to-date database documentation, forcing developers to reverse-engineer schemas from scattered DDL files, migrations, and ORM models before making any change. ## Core Features & Use Cases - Full Schema Inventory: Catalogs every table with columns, types, keys, indexes, and constraints, grouped by business domain. - Relationship & ERD Generation: Maps all cardinalities (1:1, 1:N, N:M), junction tables, and polymorphic relations, then renders Mermaid ERDs per domain plus a global overview. - Business Rule Extraction: Documents triggers, stored procedures, views, and check constraints with a confidence scale (direct DDL, inferred from ORM, or inaccessible). - Use Case: When onboarding onto a legacy system with only Laravel migrations and a few DBeaver screenshots, run this Skill to produce a complete data dictionary, ERD, and business-rules report under _reversa_sdd/database/. ## Quick Start Ask the agent to document the legacy database by analyzing the available DDL files, migrations, and ORM models and writing the ERD and data dictionary into the output folder.

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 schema automatically?▼

Point the Skill at your available schema sources such as DDL files, migrations, or ORM models. It inventories all tables, maps relationships with cardinalities, and writes a data dictionary, ERD, and business-rules report as Markdown files.

What sources can be used to reverse-engineer a database schema?▼

Supported sources include SQL DDL files, migration frameworks (Laravel, Rails, Flyway, Liquibase, Alembic, Prisma), ORM models (Eloquent, ActiveRecord, SQLAlchemy, Hibernate, TypeORM), screenshots of tools like DBeaver or pgAdmin, and read-only direct connections.

Can it connect directly to a production database?▼

Yes, but strictly in read-only mode. The instructions explicitly forbid executing INSERT, UPDATE, DELETE, or DROP statements, so only schema introspection queries are performed against a live connection.

How does it handle incomplete or uncertain schema information?▼

Every finding is tagged with a confidence scale: green for direct DDL or migrations, yellow for inference from ORM models or screenshots, and red when the information is inaccessible, so readers know what to trust.

What output files does the database documentation produce?▼

It writes erd.md with Mermaid diagrams, data-dictionary.md, relationships.md, business-rules.md, and procedures.md into the database folder under the configured output directory, defaulting to _reversa_sdd.