migration-guard

Analyze database schema migrations for lock risk, compatibility, rollback, and data preservation.

3|1|Updated Nov 29, 2025

Search Tags:#automation #rollback #database #compatibility #analysis #migration #risk

Ready to run

npx skills add https://github.com/indrasvat/claude-code-skills --skill migration-guard-indrasvat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-guard
Source: https://github.com/indrasvat/claude-code-skills/tree/main/skills/migration-guard
Command: npx skills add https://github.com/indrasvat/claude-code-skills --skill migration-guard-indrasvat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes database schema migrations for safety, evaluating lock risk, backward compatibility, rollback viability, and data preservation to prevent deployment issues.

Core Features & Use Cases

Detects migration frameworks and file changes to scope analysis
Checks for common risks: lock-heavy operations, NOT NULL without defaults, and risky column changes
Generates guidance on rollback strategies and data preservation pathways for safe migrations
Use Case: A developer reviews a new migration file to ensure it won't block writes or lose data.

Quick Start

Simply point the tool at your migration file or directory and review the auto-generated risk report.

Frequently Asked Questions about migration-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if a database schema migration will cause table locks or data loss?▼

Database schema migration safety analysis evaluates lock risk, backward compatibility, and rollback viability. Pointing the analyzer at migration files detects risky operations like lock-heavy changes and provides non-destructive remediation guidance.

What are common risks when adding NOT NULL columns without defaults in database migrations?▼

Adding NOT NULL columns without defaults risks blocking writes and breaking backward compatibility. Migration analysis detects this pattern alongside risky column changes, generating guidance on data preservation and safe deployment strategies.

Can I analyze only the database migrations that changed since the last commit?▼

Yes, migration analysis can scope to files changed since the last commit. This targets risk assessment during active development and deployment planning, reviewing only modified migration files rather than the entire directory.

How do I plan a rollback strategy for a risky database schema migration?▼

Planning a rollback strategy requires evaluating rollback viability of migration files. The analysis generates guidance on rollback pathways and data preservation techniques, ensuring safe migration reversals if deployment issues occur.

Does this migration analysis modify my database or migration files during evaluation?▼

No, migration analysis is strictly read-only. It evaluates schema migration files without modifying your database, providing non-destructive recommendations and actionable remediation guidance for safe deployment planning.

What is the best way to validate backward compatibility before deploying schema migrations?▼

Validating backward compatibility requires automated migration analysis checking for lock-heavy operations, NOT NULL constraints without defaults, and risky column changes. This read-only evaluation provides remediation guidance before deployment.