reversa-data-master

Document legacy database schemas into data dictionaries and Mermaid ERDs.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-data-master-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-data-master
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-data-master
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-data-master-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates comprehensive documentation of an existing legacy database, including tables, relationships, constraints, triggers, procedures, and a complete ERD.

Core Features & Use Cases

  • Comprehensive data dictionary generation covering tables, columns, data types, PKs/FKs, and constraints.
  • ERD generation in Mermaid format for domain-level and overall views.
  • Use cases: audit, migration planning, governance, and knowledge transfer for legacy database environments.

Quick Start

Run the reverse-engineering workflow against your database schema to produce 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 document a legacy database schema including tables, triggers, and procedures?

To document a legacy database comprehensively, this Skill reverse-engineers your schema by extracting tables, relationships, constraints, triggers, and procedures to generate a complete data dictionary and ERD.

Can I generate an ERD from existing DDL or ORM models without direct database access?

Yes, you can generate an ERD from existing DDL or ORM models. The Skill analyzes DDL, migrations, or ORM models to map relationships and produce domain-level Mermaid ERD diagrams.

What is the best way to create a data dictionary for database migration planning?

Creating a data dictionary for migration planning involves reverse-engineering the schema to extract columns, data types, primary keys, and foreign keys into a comprehensive documentation output.

Does this database reverse-engineering process support read-only database access?

Yes, the database reverse-engineering process supports read-only access. It safely targets read-only connections, DDL analysis, and ORM models to extract schema details without modifying data.

When do I need to reverse-engineer database schema constraints into a Mermaid diagram?

You need to reverse-engineer database schema constraints into a Mermaid diagram during audits, governance, or knowledge transfer to visually map complex legacy relationships and dependencies.