How do I install the Persistence Schema Reverse Engineering skill?

Run npx skillmds@latest add tuana-vn/persistence-schema-reverse-engineering in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Persistence Schema Reverse Engineering safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Persistence Schema Reverse Engineering?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Persistence Schema Reverse Engineering free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Persistence Schema Reverse Engineering?

tuana-vn (@tuana-vn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Persistence Schema Reverse Engineering by tuana-vn

Name: Persistence Schema Reverse Engineering
Author: tuana-vn

Persistence Schema Reverse Engineering

Reconstruct persistence architecture and database/data schema from current source, ORM mappings, SQL, migrations, DDL, schema bootstrap, upgrade scripts, and runtime repository wiring; distinguish code-known schema from external-only details.

tuana-vn 28582f5 3.3 KB Updated Sep 17, 2026

File contents

Persistence and Schema Reverse Engineering

Mission

Determine whether persistence exists, how code reaches it, and what schema/data model is actually supported by repository evidence.

Applicability Check

First search for:

JDBC/data sources/connections
ORM entities/mappings
repository/DAO classes
SQL/query builders
migration frameworks/scripts
DDL/schema files
embedded/test DB setup
upgrade/install scripts
table/column constants

If no persistence is materially present, record NOT_APPLICABLE with evidence and stop.

Runtime Trace

Trace representative reads and writes:

business/service
→ repository/DAO
→ ORM/query/SQL
→ connection/data source
→ table/entity/schema

Verify runtime binding of repository implementations when abstractions exist.

Schema Reconstruction

Use evidence in priority order:

active migrations/DDL/schema bootstrap
active ORM/entity mappings
production SQL/query definitions
install/upgrade scripts
tests/test schema as supporting evidence only
docs/comments as secondary evidence

Reconstruct where supported:

table/entity names
important columns/fields
data types
PK/unique keys
FKs/relationships
indexes when behaviorally relevant
read/write ownership
transaction boundaries
migration/version history

Do not invent missing columns or relationships.

Required Tables

Persistence Path

Operation	Service/Caller	Repository/DAO	Concrete Binding	Query/ORM	Data Source	Evidence

Schema Inventory

Table/Entity	Key	Important Fields	Relationships	Read By	Written By	Definition Evidence	Confidence

Schema Gaps

Question	Search Performed	Code-Known Facts	Missing External Fact	Closure State

External Schema

If the repository contains queries/mappings but not authoritative DDL:

promote only the schema facts directly required/proven by active code
mark unavailable authoritative DDL/version as external if repository search is exhausted
do not call all database schema details UNKNOWN

Output

Create/update:

docs/reverse-engineering/persistence/<scope>.md

Update evidence ledger/open questions as appropriate.

Consumer Architecture Model

Update:

docs/reverse-engineering/models/persistence_state_model.md
docs/reverse-engineering/diagrams/05_state_persistence_lifecycle.md

The model must explain ownership and behavior, not merely dump entity fields.

Capture, where applicable:

owner
→ read/write path
→ transaction/connection boundary
→ persisted entity/table/state
→ lifecycle/state transition
→ concurrency/async interaction
→ failure/recovery behavior

05_state_persistence_lifecycle.md must contain at least one evidence-linked Mermaid diagram. If persistence is not applicable, model the most material runtime state/resource/job lifecycle instead and document why persistence is NOT_APPLICABLE.

---name: persistence-schema-reverse-engineeringdescription: Reconstruct persistence architecture and database/data schema from current source, ORM mappings, SQL, migrations, DDL, schema bootstrap, upgrade scripts, and runtime repository wiring; distinguish code-known schema from external-only details.---# Persistence and Schema Reverse Engineering## MissionDetermine whether persistence exists, how code reaches it, and what schema/data model is actually supported by repository evidence.## Applicability CheckFirst search for:- JDBC/data sources/connections- ORM entities/mappings- repository/DAO classes- SQL/query builders- migration frameworks/scripts- DDL/schema files- embedded/test DB setup- upgrade/install scripts- table/column constantsIf no persistence is materially present, record `NOT_APPLICABLE` with evidence and stop.## Runtime TraceTrace representative reads and writes:```textbusiness/service→ repository/DAO→ ORM/query/SQL→ connection/data source→ table/entity/schema```Verify runtime binding of repository implementations when abstractions exist.## Schema ReconstructionUse evidence in priority order:1. active migrations/DDL/schema bootstrap2. active ORM/entity mappings3. production SQL/query definitions4. install/upgrade scripts5. tests/test schema as supporting evidence only6. docs/comments as secondary evidenceReconstruct where supported:- table/entity names- important columns/fields- data types- PK/unique keys- FKs/relationships- indexes when behaviorally relevant- read/write ownership- transaction boundaries- migration/version historyDo not invent missing columns or relationships.## Required Tables### Persistence Path| Operation | Service/Caller | Repository/DAO | Concrete Binding | Query/ORM | Data Source | Evidence ||---|---|---|---|---|---|---|### Schema Inventory| Table/Entity | Key | Important Fields | Relationships | Read By | Written By | Definition Evidence | Confidence ||---|---|---|---|---|---|---|---|### Schema Gaps| Question | Search Performed | Code-Known Facts | Missing External Fact | Closure State ||---|---|---|---|---|## External SchemaIf the repository contains queries/mappings but not authoritative DDL:- promote only the schema facts directly required/proven by active code- mark unavailable authoritative DDL/version as external if repository search is exhausted- do not call all database schema details UNKNOWN## OutputCreate/update:```textdocs/reverse-engineering/persistence/<scope>.md```Update evidence ledger/open questions as appropriate.## Consumer Architecture ModelUpdate:```textdocs/reverse-engineering/models/persistence_state_model.mddocs/reverse-engineering/diagrams/05_state_persistence_lifecycle.md```The model must explain ownership and behavior, not merely dump entity fields.Capture, where applicable:```textowner→ read/write path→ transaction/connection boundary→ persisted entity/table/state→ lifecycle/state transition→ concurrency/async interaction→ failure/recovery behavior````05_state_persistence_lifecycle.md` must contain at least one evidence-linked Mermaid diagram. If persistence is not applicable, model the most material runtime state/resource/job lifecycle instead and document why persistence is `NOT_APPLICABLE`.

Frequently asked questions