database

Plan and validate database schema changes with forward and rollback SQL migrations.

94|49|Updated Mar 25, 2026

Search Tags:#design #database #postgresql #migration #sql #data-integrity

Ready to run

npx skills add https://github.com/josipjelic/orchestrated-project-template --skill database-josipjelic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database
Source: https://github.com/josipjelic/orchestrated-project-template/tree/main/.claude/skills/database
Command: npx skills add https://github.com/josipjelic/orchestrated-project-template --skill database-josipjelic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database schema changes can be risky without measurable rollback, clear documentation, and validation. This skill guides designers and engineers through safe migrations, ensuring changes are traceable and reversible.

Core Features & Use Cases

Read current schema from DATABASE.md to understand the state before proposing changes.
Propose forward DDL and rollback DDL with rationale, including index and constraint decisions.
Document deployment risk, backfill strategy, and validation steps for production readiness.

Quick Start

Provide a ready-to-apply forward and rollback SQL migration plan for the requested schema change.

Frequently Asked Questions about database

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

FAQPage Schema

How do I plan safe database schema migrations with rollback SQL?▼

Plan safe database schema migrations by generating forward DDL and rollback SQL with rationale for index and constraint decisions. Validate data integrity, document deployment risk, and ensure changes are traceable and reversible.

What should I include in a database migration deployment risk assessment?▼

A database migration deployment risk assessment should include backfill strategy, validation steps for production readiness, and measurable rollback procedures. Document these alongside forward and rollback DDL to ensure changes are traceable and reversible.

How do I design database schema changes without breaking data integrity?▼

Design database schema changes without breaking data integrity by applying normalization rules, validating constraints, and indexing decisions. Read the current schema state before proposing changes to ensure robust database design.

Can I use this approach for PostgreSQL migration planning?▼

Yes, you can use this approach for PostgreSQL migration planning. It guides you through schema design reviews, performance considerations, and forward and rollback SQL generation specifically tailored for PostgreSQL database environments.

What's the best way to document database schema state before a migration?▼

The best way to document database schema state before a migration is to maintain a DATABASE.md file. Read the current schema from this file to understand the state before proposing changes and generating migration plans.

When do I need a backfill strategy for database migrations?▼

You need a backfill strategy for database migrations when schema changes require existing data to be populated or transformed. Include backfill logic in your migration plan alongside deployment risk assessment and validation steps for production readiness.