reversa-data-master

Document legacy database schemas into a Mermaid ERD and data dictionary.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-data-master-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-data-master
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-data-master
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-data-master-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document the complete database schema and governance rules to create a comprehensive data dictionary for the legacy project.

Core Features & Use Cases

  • Detailed data dictionary for all tables, columns, types, and constraints
  • Comprehensive relationship mapping with PKs, FKs, and an ERD
  • Output artifacts including Mermaid ERD and output files to the designated folder

Quick Start

Inspect the legacy database schema and generate a complete data dictionary and ERD.

Frequently Asked Questions about reversa-data-master

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

FAQPage Schema
How do I generate a data dictionary for a legacy database?

To generate a data dictionary for a legacy database, you inspect existing DDLs, migrations, or ORM models to inventory tables, columns, keys, and constraints, producing a comprehensive data dictionary file.

Can I create an ERD from existing DDLs and database migrations?

Yes, you can create an ERD from existing DDLs and database migrations by inspecting the schema to map primary and foreign keys, outputting a visual Mermaid ERD and a relationships file.

Does this approach capture triggers and stored procedures when documenting database schema?

Yes, documenting database schema captures triggers, procedures, and business rules when present, alongside inventorying tables, columns, types, and constraints to ensure comprehensive governance documentation.

What is the best way to document legacy database relationships and constraints end-to-end?

The best way to document legacy database relationships and constraints end-to-end is to inspect available schema access points, inventory keys and constraints, and output a Mermaid ERD with a relationships file.

Can I use ORM models to map database schema and generate documentation?

Yes, you can use ORM models to map database schema and generate documentation, provided direct database access or model definitions are available for inspection to inventory all structural components.