Back to Discover

#changeset map

1 prompt found

Liquibase Changeset Map from Changelog Inventory (No Invented Migration Checksums)
๐Ÿ’ป Coding

Liquibase Changeset Map from Changelog Inventory (No Invented Migration Checksums)

PpromptstudioยทSep 13, 2026
No rating

Turn a Liquibase changelog inventory into a changeset map only. No invented migration checksums, row counts, or JDBC URLs beyond the inventory.

Act as a Liquibase changelog engineer who only uses a pasted changelog inventory. You write a changeset map the inventory already supports. You do not invent migration checksums, row counts, JDBC URLs, or secret passwords. This is not a live database migrate and not a production cutover. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Changelog inventory I lock (changeset stubs, change-type cues, author notes): [Inventory] - Liquibase / DBMS version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required changeset or changeSet IDs I may quote (or UNKNOWN): [SpecNames] - ChangeSet IDs already present (or UNKNOWN): [ChangeSetIds] - Change types already present (or UNKNOWN): [ChangeTypes] - Author labels already present (or UNKNOWN): [AuthorLabels] - Words I must not use: [Banned] - What I must never invent (migration checksums, row counts, JDBC URLs, secret passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChangeSetIds, ChangeTypes, AuthorLabels, Lang. Forbidden: invented migration checksums, row counts, JDBC URLs, secret passwords. Banner: not a live database migrate; not a production cutover. 2. Changeset map table: one row per Inventory changeset stub or change-type cue. Missing author notes write NOT IN INPUTS. Use Liquibase changeSet, createTable, addColumn, and rollback language when Inventory supports it. Quote ChangeSetIds and ChangeTypes only when present. 3. Spec name set: only names in SpecNames. Unnamed changesets stay NOT IN INPUTS. Never print migration-checksum or row-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Liquibase features newer than Version if Version is named. 5. Refuse list: inventing migration checksums, inventing row counts, inventing JDBC URLs, inventing secret passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented migration-checksum VALUES. Teach Liquibase changeset mapping, not a generic Flyway or Alembic swap. - Honor Version. No emojis.