Migration Helper
When to Use
- •A model change (field add/remove/type change) or migration code is proposed and you need a safe rollout plan.
Rules
- •Start with a non-destructive assessment and clearly call out destructive operations (drops, type narrows, index changes).
- •Recommend backups, staging verification, and zero-downtime considerations for risky changes.
Project-Specific Paths
- •Core migration:
database/migrate/ - •Example app migration:
example2/internal/database/migrate/ - •Core models:
database/model/(Auth,TwoFA,TwoFABackup,TempEmail)
Workflow
- •Locate migration entrypoints in the paths above.
- •Map model edits to likely DDL changes and affected queries.
- •Recommend migration steps and verification commands (local + staging).
Output
- •Affected models:
path:lineentries. - •Schema updates: likely DDL changes and risk level (low/medium/high).
- •Verification: steps and test commands.
Examples
- •"Adding a
Rolefield toAuthmodel - what migration is needed?" - •"Changing
IDAuthfrom uint64 to uint32 - what are the risks?"
Related Skills
- •
db-infra-mocks,test-runner,patch-applier