schema-migration

Migrate PostgreSQL schemas with explicit, documented, reversible changes.

Updated Aug 23, 2026

Search Tags:#typescript #database #postgresql #migration #sql #schema-migration

Ready to run

npx skills add https://github.com/Deadpool042/Creatyss --skill schema-migration-deadpool042

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schema-migration
Source: https://github.com/Deadpool042/Creatyss/tree/main/.backup/agents-audit/codex-skills.bak/schema-migration
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill schema-migration-deadpool042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Faire évoluer le schéma PostgreSQL de Creatyss via une migration explicite, sobre, compatible avec l’existant et alignée sur la doctrine actuelle du repo ainsi que sur le lot demandé.

Core Features & Use Cases

Migration explicite: ajouter ou modifier des colonnes, contraintes, index et tables avec traçabilité et reversibilité.
Compatibilité et gouvernance: préserver la compatibilité avec les modèles existants, les repositories et les typings TypeScript lors des transitions.
Cas d'usage: faire évoluer le schéma pour supporter une nouvelle fonctionnalité sans rupture du modèle client.

Quick Start

Exécutez une migration explicite sur le schéma PostgreSQL pour aligner le modèle courant avec le lot ciblé, en préservant la compatibilité et en documentant chaque changement.

Frequently Asked Questions about schema-migration

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

FAQPage Schema

How do I add or alter PostgreSQL columns without breaking existing TypeScript models?▼

To alter PostgreSQL columns without breaking TypeScript models, you perform an explicit schema migration that preserves transitional compatibility. This approach ensures legacy repositories and typings remain functional during the database schema evolution.

What is the best way to manage explicit schema migrations in PostgreSQL?▼

The best way to manage explicit schema migrations in PostgreSQL is by applying dedicated, traceable, and reversible migration scripts. This process aligns database changes with architectural guidelines while evolving tables, columns, and constraints safely.

When do I need a dedicated migration script for PostgreSQL schema changes?▼

You need a dedicated migration script for PostgreSQL schema changes when evolving the database to support new features without causing a rupture in the client model. It ensures every structural change is documented and reversible.

Can I update database constraints and indexes while maintaining compatibility with legacy repositories?▼

Yes, you can update database constraints and indexes while maintaining compatibility with legacy repositories. The migration process explicitly preserves alignment with existing TypeScript typings and project doctrine during structural transitions.

Why should I use explicit schema migrations instead of direct database modifications?▼

You should use explicit schema migrations instead of direct modifications to ensure traceability, reversibility, and governance. Direct changes risk breaking legacy models, whereas a dedicated script documents changes and aligns with architectural guidelines.

Does schema migration work with existing TypeScript repositories during database transitions?▼

Yes, schema migration works with existing TypeScript repositories by ensuring transitional compatibility. It applies structural database changes through documented scripts that explicitly preserve current typings and repository functionality.