Migrate
Plan and execute codebase or database migrations step by step with safety checks.
by AgentVoltv1.0.0Published 1y ago3 installs
Free to sign up · every skill included with AgentVolt Pro
Before & after
Same prompt, same agent — the only difference is the skill.
Prompt“Plan a safe migration from MySQL to PostgreSQL without downtime”
Beforegeneric AI agent
A database migration like this is complex and requires careful planning. You'll want to start by backing up all your data, then setting up a parallel PostgreSQL environment. Test the schema migration and data conversion in a staging environment first. Make sure to test your application thoroughly to ensure it works with PostgreSQL. You should plan for a cutover window, ideally during low-traffic periods. Having a rollback plan is critical in case something goes wrong. You might want to perform a dry run of the entire migration process. It's important to notify stakeholders and plan communication around the migration. Would you like help thinking through any specific part of this plan?
Afterwith Migrate
MIGRATION PLAN: MySQL to PostgreSQL PRE-MIGRATION VALIDATION Database size: 240 GB Peak concurrent connections: 45 Latest backup: 2 hours old, restore tested Application: Connection strings NOT yet updated (blocking issue) MySQL-specific functions found: 12 (FIND_IN_SET, etc.) requiring rewrite Timeline impact: +4 days for function conversion PHASED CUTOVER PHASE 1 (Day 1): PostgreSQL provisioned. Schema migrated via pgloader. Data loaded (6-hour ETA for 240 GB). Indexes built and tested. PHASE 2 (Day 2-3): Staging app tested. Query performance benchmarked. Stored procedures rewritten and validated. PHASE 3 (Day 4, 2 AM): Read traffic redirected to PostgreSQL (writes stay on MySQL for 2 hours). Monitor errors. Flip writes at 4 AM. PHASE 4 (Day 4, 4 AM): All traffic on PostgreSQL. Monitor for 4 hours. Keep MySQL online as hot standby for 48 hours. PHASE 5 (Day 6): Decommission MySQL after final validation. SAFETY CHECKPOINTS Monitor every 15 minutes: Connection count, query latency, error rate Automatic rollback trigger: Any metric fails Rollback tested and timed: 8 minutes to revert COMMUNICATION 2 weeks prior: Announce maintenance to users 24 hours prior: Warn of 2-4 hour maintenance window (2 AM)
About this skill
name: migrate description: Use when -
Migrate
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the migrate skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Migrate; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
SKILL.md
---
name: migrate
description: Use this skill when planning or executing a codebase or database migration that needs staged rollout, dependency ordering, and rollback safety.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Migrate
Plans and executes codebase or database migrations step by step, with explicit safety checks at every stage so nothing ships without a tested rollback path.
## When to use
… (sign up to view the full skill)Sign up to view, copy, and install the full skill
Featured in
More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Development
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Development
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Development
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.
Development