managing-database-migrations

Generate, apply, and rollback versioned database migrations across PostgreSQL, MySQL, SQLite, and MongoDB.

3|Updated Feb 13, 2026

Search Tags:#versioning #rollback #database #postgresql #migrations #schema #sql

Ready to run

npx skills add https://github.com/ahiendz/DuAnCuoiKhoa --skill managing-database-migrations-ahiendz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: managing-database-migrations
Source: https://github.com/ahiendz/DuAnCuoiKhoa/tree/main/.agents/skills/managing-database-migrations
Command: npx skills add https://github.com/ahiendz/DuAnCuoiKhoa --skill managing-database-migrations-ahiendz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It enables safe, auditable management of database schema changes through versioned migrations.

Core Features & Use Cases

Generate timestamped migrations with up and down scripts for PostgreSQL, MySQL, SQLite, and MongoDB.
Apply migrations, rollback changes, and track schema evolution across environments.
Validate migration files and ensure transactional execution for safety.

Quick Start

Create a new timestamped migration file and apply it to your target database.

Frequently Asked Questions about managing-database-migrations

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

FAQPage Schema

How do I manage database schema changes safely?▼

Database schema changes are managed safely through versioned migrations, generating timestamped up and down scripts to ensure auditable evolution and rollback across environments.

Can I generate rollback scripts for PostgreSQL and MongoDB?▼

Yes, rollback scripts are generated for PostgreSQL, MySQL, SQLite, and MongoDB. Each migration includes paired up and down scripts to reverse schema changes when needed.

How do I apply database migrations and track schema evolution?▼

You apply database migrations through transactional execution, validating file formats first to ensure safety. This tracks schema evolution reliably across your target environments.

What is the best way to handle versioning for SQL schema migrations?▼

The best way to handle SQL schema versioning is using timestamped migration files. This ensures safe, auditable schema evolution by applying changes transactionally with rollback support.

Does this approach validate migration files before applying them?▼

Yes, migration files are validated for correct format before execution. This validation, combined with transactional execution, ensures that database schema changes are applied safely.

When do I need versioned migrations for my database?▼

You need versioned migrations when evolving database schemas across environments. They provide an auditable history of changes and enable safe rollbacks if an applied schema modification fails.