Map legacy database tables and columns to a new schema.
npx skills add https://github.com/saajunaid/junai --skill schema-migration-saajunaid
Please help me install this Agent Skill. Skill: schema-migration Source: https://github.com/saajunaid/junai/tree/main/.github/skills/data/schema-migration Command: npx skills add https://github.com/saajunaid/junai --skill schema-migration-saajunaid
Migrate an application's data access layer to a new database schema without data loss, preserving functional parity during restructuring and upgrade cycles.
Provide the legacy and target schema details and request a complete migration plan.
High-intent search queries and answers about installing and using this skill.
A schema migration plan with zero data loss involves read-only analysis of both schemas to map legacy tables and columns to targets, translate dependent queries, and update the application abstraction layer. It validates mappings with a parity plan and documents changes for safe rollout.
Data mapping during schema restructuring identifies legacy tables and columns to assign them to their correct targets in the new schema. This read-only discovery process creates a schema manifest that guides the abstraction layer update plan to minimize risk during the migration.
To translate dependent queries during a schema upgrade, you apply read-only analysis to both the legacy and target schemas. You map the old data structures to the new ones and update the application's abstraction layer accordingly, ensuring no DDL or DML is executed during the migration.
Schema migration using this read-only analysis approach explicitly ensures no DDL or DML is executed during the migration. It focuses on generating a mapping manifest, updating the abstraction layer plan, and validating functional parity through testing before actual rollout.
The best way to ensure functional parity during database restructuring is to validate mappings with an end-to-end parity testing plan. This involves mapping legacy tables to targets, translating dependent queries, and documenting all changes for a safe and comprehensive rollout.
Yes, schema migration updates an application's data access layer by creating a schema manifest and abstraction-layer update plan to minimize risk. It relies on read-only analysis and parity testing to ensure functional parity during restructuring and upgrade cycles without direct database execution.
cliffthelinGenerate ERD, data dictionary, relationship map, and business-rules inventory from schema evidence.
ConsiliencyProvide framework-agnostic Supabase patterns for RLS, realtime, storage, edge functions, and migrations.
Zidane786List database tables, columns, data types, and foreign key relationships.
hendrax5Create timestamped, idempotent SQL and Alembic migrations for zero-downtime schema changes.
