cambium-database-migrations

Generates SQL scripts for Git-managed PostgreSQL migrations with manual Railway deployment and ALTER patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-database-migrations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cambium-database-migrations
Source: https://github.com/ecnepsyroc-bot/Dejavara/tree/main/deploy/skills/cambium-database-migrations
Command: npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-database-migrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents destructive or failing deployments caused by EF Core and PostgreSQL schema drift, missing columns or tables on Railway, and accidental use of automatic startup migration that can recreate or break production schemas.

Core Features & Use Cases

  • Manual-first migration workflow: generate SQL from EF Core migrations, review for destructive changes, and apply to Railway deliberately instead of using MigrateAsync.
  • Self-healing ALTER pattern: per-column ALTER with try/catch to add critical auth-related columns at startup and verification to avoid single-point failures.
  • Pre-push and audit controls: run schema checks, keep manual migration records, and validate Railway state before pushing code that changes the schema.
  • Use Case: use this Skill when adding entities or columns, debugging PostgreSQL errors 42703 or 42P01, or preparing a safe Railway deployment.

Quick Start

Generate the SQL script from your EF Core migration, review it for destructive operations, and apply the resulting SQL manually to the Railway database.

Frequently Asked Questions about cambium-database-migrations

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

FAQPage Schema
Why does my EF Core deployment fail on Railway with PostgreSQL error 42703 or 42P01?

PostgreSQL errors 42703 and 42P01 on Railway indicate EF Core schema drift from missing columns or tables. This Skill helps debug these issues by generating manual migration SQL and applying self-healing ALTER patterns to safely update the production database schema.

How do I prevent EF Core MigrateAsync from breaking my production PostgreSQL schema on Railway?

To prevent destructive automatic startup migration via MigrateAsync, use a manual-first workflow. This Skill generates SQL scripts from EF Core migrations for deliberate review and manual application to Railway, avoiding accidental schema recreation or breaking changes in production.

What's the best way to add new columns to a PostgreSQL database on Railway without downtime?

The best way to add columns safely is using a self-healing ALTER pattern. This Skill provides per-column ALTER statements with try/catch logic and verification at startup, ensuring critical auth-related columns are added without causing single-point failures during Railway releases.

Can I run pre-push schema checks for EF Core migrations before deploying to Railway?

Yes, you can run pre-push schema checks to validate Railway state before deploying. This Skill supports keeping manual migration records and running schema audits to verify your PostgreSQL database state prior to pushing code that changes the schema.

When do I need to manually apply EF Core migration SQL instead of using automatic migrations?

You need manual application when adding entities or columns, debugging schema drift, or preparing safe Railway releases. This Skill generates migration SQL for you to review for destructive operations and apply deliberately, bypassing risky automatic startup migration behaviors.