db-migrations

Enforce non-destructive, reversible database schema migrations with naming conventions.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/sobhanashine/nazarato --skill db-migrations-sobhanashine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-migrations
Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/db-migrations
Command: npx skills add https://github.com/sobhanashine/nazarato --skill db-migrations-sobhanashine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage database migrations safely, ensuring that changes to the database schema are reversible and do not harm the data.

Core Features & Use Cases

  • Non-Destructive Migrations: Prevents destructive changes without proper backups.
  • Reversible Changes: Ensures every migration has a corresponding rollback.
  • Schema Naming Conventions: Enforces consistent and readable naming for tables, columns, and indexes.
  • Indexing Discipline: Recommends indexing new columns for performance.

Quick Start

Run the db-migrations skill to apply a new migration to your database.

Frequently Asked Questions about db-migrations

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

FAQPage Schema
How do I ensure my database schema changes are reversible?

Reversible database schema changes are enforced by generating a corresponding rollback for every migration. This ensures any applied schema migration can be safely undone without harming existing data.

What is a non-destructive database migration?

A non-destructive database migration applies schema changes without permanently losing data. It prevents destructive schema modifications unless proper backups are verified, ensuring safe database evolution.

How do I enforce naming conventions for database schema objects?

Naming conventions for database schema objects are enforced during the migration process. The skill checks table, column, and index names against consistent readability rules to maintain schema hygiene.

Why do I need to add indexes when creating new database columns?

Adding indexes to new database columns is recommended to maintain query performance. This indexing discipline ensures newly introduced schema fields do not cause database lookup bottlenecks.

Can I use this to manage database schema evolution for existing tables?

Yes, you can manage schema evolution for existing tables by applying non-destructive changes. The skill ensures your schema updates are safe, reversible, and follow proper naming and indexing standards.

What are the limitations of automated reversible schema migrations?

Automated reversible schema migrations require a defined rollback path and may block destructive changes if backups are missing. Complex data transformations might still need manual intervention to prevent data loss.