reversa-data-master

Generate ERD, data dictionary, relationship map, and business-rules inventory from schema evidence.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-data-master-cliffthelin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-data-master
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/skills/reversa/reversa-data-master
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-data-master-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reversa-data-master converts incomplete or messy database knowledge into complete, audit-friendly documentation, so teams can understand schemas, relationships, and embedded business rules without risky database access.

Core Features & Use Cases

  • Database inventory & table documentation: Produces a structured inventory of tables/collections and their purposes, grouped by domain.
  • Deep schema extraction: Captures columns, types, nullability, defaults, primary keys, foreign keys, indexes, and constraints from available DDL/migrations/ORM models/screenshots.
  • Relationship & business rules mapping: Documents cardinalities, join/polymorphic relationships, and database-level logic such as triggers, stored procedures/functions, and views.
  • ERD generation: Creates a Mermaid ER diagram (full and/or partial by domain) suitable for downstream System Design Documents.

Quick Start

Use the reversa-data-master skill to generate complete database documentation artifacts from your available DDL, migration files, ORM models, or read-only database metadata sources.

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 an ERD from existing database migrations and ORM models?

Generating an ERD from migrations and ORM models involves extracting schema details like columns, keys, and constraints, then producing Mermaid ER diagrams grouped by domain. This Skill processes available DDL and schema files to output visual relationship maps without requiring live database access.

What is the best way to document legacy database business rules and stored procedures?

The best way to document legacy database business rules and stored procedures is through read-only inspection of triggers, functions, and views. This Skill extracts database-level logic from schema evidence and generates a structured inventory of business rules and procedures in markdown format.

Can I extract a data dictionary and relationship map without executing write operations on the database?

Yes, you can extract a data dictionary and relationship map without write operations. This Skill performs read-only inspection of schema evidence like DDL and ORM models, ensuring no write, delete, or drop operations are executed during the documentation process.

Does this database documentation tool work with DDL files and screenshots for schema extraction?

Yes, this database documentation tool works with DDL files and screenshots for schema extraction. It accepts DDL, migration files, ORM models, and screenshots as schema evidence to capture columns, types, constraints, and indexes for the final data dictionary artifacts.

What are the limitations of using read-only inspection for database schema extraction?

A limitation of using read-only inspection for database schema extraction is reliance on available schema evidence like DDL or ORM models rather than a live connection. If schema evidence is incomplete, the resulting ERD and business-rules documentation may lack full coverage of constraints and triggers.