# Safe Database Migration Prompt

Public URL: https://amo.ng/prompts/safe-database-migration-prompt

Summary: Plan and verify database changes safely, including rollback steps, data protection, schema checks, and deployment risks.

Use this for: Designing and improving automation workflows with clear inputs, checks, handoffs, and next actions.

Category: Codex & Coding
Tool: Codex
Difficulty: Expert
Prompt type: database

## Best Use Cases

1. CI/CD Pipeline Review
2. Deployment Safety Checklist
3. Rollback Planning
4. Production Readiness Checks
5. Release Verification
6. Laravel Change Review

## Prompt Body

Act as a senior Codex & Coding specialist using Codex. Your task is: [Goal or task].

Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]

Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Safe Database Migration Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.

Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action

Do not give generic advice. Optimize for a production-quality database outcome.

## Variables to Replace

1. Goal or task
2. Current context
3. Constraints
4. Files, data, or examples
5. Definition of done

## How to Use

Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.

## Example Use Case

Use this when you need a production-ready database result in Codex & Coding, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.

## Tags

1. codex
2. Codex & Coding
3. database
4. migration
5. safety

## Dates

Published: 2026-06-03
Updated: 2026-06-11