crud-migration

Centralize PowerX CoreX database migrations through a single Go entry point.

357|65|Updated Jul 29, 2022
One-click install
npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crud-migration
Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/crud/migration
Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and enforces the PowerX CRUD migration process to avoid scattered, inconsistent database changes across modules.

Core Features & Use Cases

  • Centralized migration entry: MigrateCoreModels and agent migrations are orchestrated from a single place.
  • Guardianship and constraints: Enforces explicit entry points and production safeguards to prevent unsafe migrations.
  • Real-world use: Teams align all domain migrations under the single migration.go path and reduce drift.

Quick Start

Follow the embedded rules to align all CoreX model migrations through the centralized migration entry and avoid scattered migration files.

Frequently Asked Questions about crud-migration

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

FAQPage Schema
How do I centralize database migrations for PowerX CoreX to prevent model drift?

Centralize database migrations for PowerX CoreX by enforcing a single migrate entry at cmd/database/migrate.go and a centralized migration registrar at pkg/corex/db/database/migration.go. This prevents model drift by consolidating domain-specific migration files into one orchestrated path.

Why does my PowerX CoreX stack have scattered domain-specific migration files?

Scattered domain-specific migration files occur without centralized CRUD migration enforcement. Requiring a single migration registrar eliminates scattered files by orchestrating MigrateCoreModels and agent migrations from one explicit entry point.

Can I deliver raw SQL database migrations within a PowerX CoreX stack?

Raw SQL database migrations are not delivered within the PowerX CoreX stack. Centralized CRUD migration enforces production safeguards by requiring explicit entry definitions and centralized mounting to prevent unsafe database changes.

What is the best way to orchestrate MigrateCoreModels and agent migrations in PowerX?

The best way to orchestrate MigrateCoreModels and agent migrations in PowerX is aligning all domain migrations under a single migration.go path. This enforces centralized mounting and explicit entry definitions to reduce drift.

Does centralizing CRUD migrations in PowerX require explicit entry definitions?

Centralizing CRUD migrations in PowerX requires explicit entry definitions. It enforces explicit entry points and production safeguards to satisfy requirements for centralized mounting and avoid scattered domain-specific migration files.

When do I need to enforce a centralized migration registrar for PowerX CoreX models?

You need to enforce a centralized migration registrar for PowerX CoreX models when consolidating database migrations to prevent drift. It requires a single migrate entry and avoids scattered domain-specific migration files across modules.