| name | migrate |
| description | Safely apply database or data migrations with backup and rollback notes. |
| argument-hint | migration file, SQL, version, or environment |
| license | MIT |
| metadata | {"category":"operations","tags":["database","migration","rollback"],"effort":"high","side_effect":"data-migration","explicit_invocation":true,"skill_version":1,"prompt_version":"pfo-migrate-v1","eval_dataset":"tests/eval-datasets/migrate.json"} |
Migrate
Apply migrations carefully.
Process
- Identify target database and environment.
- Inspect migration and current schema.
- Require explicit confirmation for production.
- Create or verify backup where practical.
- Apply migration.
- Verify schema and application health.
- Document rollback.
Self-validation
Before final output, verify:
- Route, side-effect, and confirmation requirements match metadata.
- Required artifacts or read-only result are explicit.
- Verification, blockers, and next route are stated.
Rules
- No production mutation without confirmation.
- No destructive migration without rollback discussion.
- Prefer transactional migrations when supported.