migration
Plan and execute database or framework migrations with rollback strategies
Works with
--- name: migration description: Plan and execute database or framework migrations with rollback strategies license: MIT --- ## What I do - Analyze current schema or framework version - Plan migration steps with proper ordering - Generate migration files in the project's format - Create rollback strategies for each step - Validate data integrity considerations ## When to use me Use this skill when you need to: - Create database migrations (schema changes, data migrations) - Upgrade a framework or library to a new major version - Migrate from one technology to another (e.g., ORM switch) ## Database Migration Process 1. **Analyze**: Read current schema and understand relationships 2. **Plan**: List all changes needed, order by dependencies 3. **Generate**: Create migration files in the project's format: - Prisma: `prisma/migrations/` - TypeORM: `src/migrations/` - Django: `app/migrations/` - Flyway: `db/migration/` - Liquibase: `db/changelog/` 4. **Rollback**: For each migration, create the inverse operation 5. **Validate**: Check for data loss risks and foreign key constraints ## Framework Migration Process 1. **Inventory**: List all breaking changes from changelog 2. **Assess**: Identify affected code in the project 3. **Plan**: Create ordered list of changes 4. **Execute**: Make changes incrementally 5. **Test**: Verify after each step ## Migration File Template ```sql -- Migration: description -- Created: YYYY-MM-DD -- Author: [generated] -- UP ALTER TABLE ...; -- DOWN (rollback) ALTER TABLE ...; ``` ## Rules - Always include rollback/down migrations - Never drop columns without data backup strategy - Consider zero-downtime migration patterns for production - Test migrations on a copy of production data - Document any manual steps required
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
