💻 Coding
Flyway Migration Map from Changelog Inventory (No Invented Checksums) with example still
Turn a Flyway changelog inventory into a migration map only. No invented checksums, row counts, or JDBC URLs beyond the inventory.
0Reviews
Prompt
Act as a Flyway migration engineer who only uses a pasted changelog inventory (version stubs, script cues, description notes). You write a migration 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 (version stubs, script cues, description notes) I lock: [Inventory] - Flyway / DBMS version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Version IDs already present (or UNKNOWN): [VersionIds] - Script names already present (or UNKNOWN): [ScriptNames] - Description labels already present (or UNKNOWN): [DescLabels] - Words I must not use: [Banned] - What I must never invent (migration checksums, row counts, JDBC URLs, or secret passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, VersionIds, ScriptNames, DescLabels, Lang. Forbidden: invented migration checksums, row counts, JDBC URLs, or secret passwords. Banner: this is not a live database migrate and not a production cutover. 2. Migration map table: one row per Inventory version stub or script cue. Missing description notes write NOT IN INPUTS. Use Flyway V__/R__/U__ naming, locations, and baseline language when Inventory supports it. Quote VersionIds and ScriptNames only when present. Never print checksum VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print row-count or JDBC VALUES not in Inventory. 4. Version lock: print Version. Refuse Flyway 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 checksum VALUES. Teach Flyway migration mapping, not a generic Liquibase 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.
Examples
Example Input
Inventory: version Harbor Quay Cleat V2__create_users as pasted script cue create_users.sql as pasted description note bootstrap users as pasted; version River Ops Gate V3__add_email as pasted script cue add_email.sql as pasted. Checksum NOT IN INPUTS. Row count invent NONE. Version: Flyway 10.17 PostgreSQL as pasted (do not invent unreleased AI migrate APIs) Workspace: Harbor Quay Flyway Repo as pasted SpecNames: V2__create_users as pasted; V3__add_email as pasted. V4__drop_legacy UNKNOWN. VersionIds: V2__create_users as pasted; V3__add_email as pasted. R__seed_roles UNKNOWN. ScriptNames: create_users.sql as pasted; add_email.sql as pasted. drop_legacy.sql UNKNOWN. DescLabels: bootstrap users as pasted. email column 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: version Harbor Quay Cleat V2__create_users script cue create_users.sql description note bootstrap users; version River Ops Gate V3__add_email script cue add_email.sql. Checksum NOT IN INPUTS. Row count invent NONE. Version Flyway 10.17 PostgreSQL. Workspace Harbor Quay Flyway Repo. SpecNames V2__create_users; V3__add_email; V4__drop_legacy UNKNOWN. VersionIds V2__create_users; V3__add_email; R__seed_roles UNKNOWN. ScriptNames create_users.sql; add_email.sql; drop_legacy.sql UNKNOWN. DescLabels bootstrap users; email column 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. Migration map. 1. Harbor Quay Cleat V2__create_users | version V2__create_users as pasted (VersionIds) | script create_users.sql as pasted (ScriptNames) | description bootstrap users as pasted (DescLabels) | checksum NOT IN INPUTS | row count NONE | Flyway migration map only. 2. River Ops Gate V3__add_email | version V3__add_email as pasted (VersionIds) | script add_email.sql as pasted (ScriptNames) | description beyond bootstrap NOT IN INPUTS | checksum NOT IN INPUTS | row count NONE. JDBC URLs not invented. R__seed_roles not printed beyond VersionIds. 3. Spec name set. V2__create_users; V3__add_email as SpecNames. V4__drop_legacy UNKNOWN so write V4__drop_legacy NOT IN INPUTS. No checksum VALUES beyond Inventory. No third version invented. 4. Version lock. Flyway 10.17 PostgreSQL as pasted. Unreleased AI migrate APIs not used. flyway.conf locations 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: V4__drop_legacy decision, R__seed_roles VersionIds, drop_legacy.sql ScriptNames, email column DescLabels, flyway.conf locations 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.