Codex Ship: Database Migration
Plan a reversible data migration with repository-aware safeguards.
- Best tool
- Codex
- Difficulty
- Beginner
- Use case
- Database Migration
- Prompt type
- Reusable prompt
What this prompt does
Plan a reversible data migration with repository-aware safeguards. It is designed for database migration and works best with Current Codex coding model configured for the repository.
Copy-ready prompt
This is a reusable natural-language prompt for Codex, not a shell command.
Work in the repository at [REPOSITORY_OR_PATH]. Goal: plan a reversible data migration. Context: [CONTEXT]. Constraints: [CONSTRAINTS]. Definition of done: [ACCEPTANCE_CRITERIA].
Run relevant checks, summarize the diff, call out risks and rollback, and prepare reviewer-facing notes.
Read applicable AGENTS.md guidance and use Codex’s inspection, editing, and verification workflow; keep approval boundaries and the user’s working tree intact.
First read the repository instructions and relevant framework documentation. Preserve unrelated user changes. State assumptions, cite files and lines for findings, and ask only when a missing decision would materially change the result. Do not invent APIs, commands, flags, test results, or file contents. Deliver: schema steps, backfill, validation, rollback, and monitoring. Run the repository’s relevant formatting, lint, type, test, and build checks when authorized, and report exact results.
How to use it
Replace the bracketed variables with real context for database migration. Attach or paste source material when available, and verify consequential facts before acting.
Related prompts
Codex Inspect: Codebase MapMap architecture, entry points, data flow, and ownership boundaries with repository-aware safeguards.Codex Debug: Bug InvestigationReproduce and isolate a reported defect with repository-aware safeguards.Codex Inspect: Integration TestsDesign integration coverage across boundaries with repository-aware safeguards.Codex Review: Performance ProfileFind and verify a performance bottleneck with repository-aware safeguards.
