💻 Coding

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

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

0.0
0Reviews
P
September 13, 2026

Prompt

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.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

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

Examples

Example Input

Inventory: changeset Harbor Quay Cleat create-users as pasted change-type cue createTable as pasted author note ops-bot as pasted; changeset River Ops Gate add-email as pasted change-type cue addColumn as pasted. Migration checksum NOT IN INPUTS. Row count invent NONE.
Version: Liquibase 4.27 PostgreSQL as pasted (do not invent unreleased AI migrate APIs)
Workspace: Harbor Quay Liquibase Repo as pasted
SpecNames: create-users as pasted; add-email as pasted. drop-legacy UNKNOWN.
ChangeSetIds: create-users as pasted; add-email as pasted. seed-roles UNKNOWN.
ChangeTypes: createTable as pasted; addColumn as pasted. createIndex UNKNOWN.
AuthorLabels: ops-bot as pasted. dba-lead UNKNOWN.
Banned: guaranteed row count, checksum invent, jdbc invent, password invent
Never: invent migration checksums, invent row counts, invent JDBC URLs, invent secret passwords
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: changeset Harbor Quay Cleat create-users change-type cue createTable author note ops-bot; changeset River Ops Gate add-email change-type cue addColumn. Migration checksum NOT IN INPUTS. Row count invent NONE. Version Liquibase 4.27 PostgreSQL. Workspace Harbor Quay Liquibase Repo. SpecNames create-users; add-email; drop-legacy UNKNOWN. ChangeSetIds create-users; add-email; seed-roles UNKNOWN. ChangeTypes createTable; addColumn; createIndex UNKNOWN. AuthorLabels ops-bot; dba-lead UNKNOWN. Lang English. Banner: not a live database migrate; not a production cutover. Forbidden: invented migration checksums, row counts, JDBC URLs, secret passwords, guaranteed row count, checksum invent, jdbc invent, password invent.

2. Changeset map.
1. Harbor Quay Cleat create-users | changeSet create-users as pasted (ChangeSetIds) | changeType createTable as pasted (ChangeTypes) | author ops-bot as pasted (AuthorLabels) | migration checksum NOT IN INPUTS | row count NONE | Liquibase changeset map only.
2. River Ops Gate add-email | changeSet add-email as pasted (ChangeSetIds) | changeType addColumn as pasted (ChangeTypes) | author note beyond ops-bot NOT IN INPUTS | migration checksum NOT IN INPUTS | row count NONE.
JDBC URLs not invented. createIndex not printed beyond ChangeTypes.

3. Spec name set. create-users; add-email as SpecNames. drop-legacy UNKNOWN so write drop-legacy NOT IN INPUTS. No migration-checksum VALUES beyond Inventory. No third changeset invented.

4. Version lock. Liquibase 4.27 PostgreSQL as pasted. Unreleased AI migrate APIs not used. includeAll paths NOT IN INPUTS.

5. Refuse. Checksum invent: refused. Row invent: refused. JDBC invent: refused. Password invent: refused. Guaranteed row count: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: drop-legacy decision, seed-roles ChangeSetIds, createIndex ChangeTypes, dba-lead AuthorLabels, includeAll path if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...