AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Db Migration Strategy

skill-kentoshimizu-sw-agent-skills-db-migration-strategy · by KentoShimizu

Schema migration strategy workflow for sequencing changes, compatibility windows, and rollback-safe rollout in live systems. Use when schema evolution impacts running services; do not use for static greenfield schemas without deployment constraints.

↗ Repository
— No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-kentoshimizu-sw-agent-skills-db-migration-strategy

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Db Migration Strategy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DB Migration Strategy

Overview

Use this skill to evolve schemas in production without service disruption or hidden data corruption.

Scope Boundaries

  • Schema changes affect live read/write paths.
  • Multiple service versions must coexist during rollout.
  • Data backfill or contract transition is required.

Core Judgments

  • Migration pattern: expand-contract, dual-write, shadow-read, or phased cutover.
  • Compatibility window duration and supported versions.
  • Backfill approach and execution safety.
  • Rollback semantics and data reconciliation strategy.

Practitioner Heuristics

  • Prefer additive/compatible changes before destructive cleanup.
  • Separate schema deployment from application behavior switch.
  • Dual-write without reconciliation plan is a corruption risk.
  • Large backfills need throttling and progress observability tied to business impact.

Workflow

  1. Define change classes: additive, transitional, destructive.
  2. Sequence schema and application releases for compatibility.
  3. Plan data migration/backfill and failure handling.
  4. Define cutover trigger and rollback decision points.
  5. Execute deprecation/removal only after compatibility window closes.
  6. Document residual migration debt and retirement deadlines.

Common Failure Modes

  • Breaking changes shipped before all consumers are updated.
  • Backfill jobs compete with production traffic and cause incidents.
  • Rollback plan restores code but not data semantics.

Failure Conditions

  • Stop when compatibility window cannot be supported operationally.
  • Stop when rollback semantics for migrated data are undefined.
  • Escalate when migration risk exceeds release risk tolerance.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills