database-migration-risk-review
Skill0 starsChanged 5 months agoMITView on GitHub
Use when reviewing schema migrations, SQL changes, data backfills, index changes, or rollout plans for data loss risk, locking, rollback gaps, validation checks, and production safety.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when schema, data, index, or backfill changes need production-safety review.
- Distinctive: line 15
Do not use when the task is general database modeling with no migration or rollout action.
- Distinctive: line 27
Check forward and backward compatibility with application code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Database Migration Risk Review
Purpose
Find practical risks in database migrations before they reach production.
Fit
- Use when schema, data, index, or backfill changes need production-safety review.
- Do not use when the task is general database modeling with no migration or rollout action.
Inputs
- Migration files, SQL snippets, schema diff, backfill plan, or rollout notes.
- Database type, table size, traffic patterns, and deployment process if available.
- Rollback expectations and validation commands.
Workflow
- Classify the migration type: schema, data, index, backfill, constraint, or cleanup.
- Identify locking, data loss, long-running query, and compatibility risks.
- Check forward and backward compatibility with application code.
- Recommend validation queries and rollout sequencing.
- State rollback limits honestly.
Output
Produce Markdown with:
- Migration Snapshot
- Risk Map
- Compatibility Review
- Validation Checks
- Rollout Plan
- Rollback Notes
- Open Questions
Validation
- Data loss risks are explicit.
- Locking and runtime impact are considered.
- Rollback is not promised when impossible.
- Validation checks are concrete.
- Unknown table size or traffic is flagged as a risk.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.