Skills database-migration
๐Ÿ“ฆ

database-migration

Content revision r2 Safe โš™๏ธ External commands

Plan Reliable Database Migrations

Database changes can cause data loss, downtime, or difficult rollbacks. This skill creates migration plans and ORM examples with validation and recovery steps.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "database-migration" from https://skillstore.io/skills/sickn33-database-migration.md and its manifest at https://skillstore.io/api/skills/sickn33-database-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "database-migration". Add a required status field to a populated users table.

Expected outcome:

  • Plan: add a nullable field, backfill active records in batches, then enforce the default and required constraint.
  • Rollback: remove the constraint first, preserve exported values, then remove the field after approval.
  • Validation: compare row counts, null counts, and application writes before cleanup.

Using "database-migration". Rename the name field to full_name without downtime.

Expected outcome:

  • Phase one adds full_name while the current application continues using name.
  • Phase two deploys dual writes, backfills existing rows, and verifies both values.
  • Phase three switches reads, monitors errors, and removes name only after the rollback window closes.

Using "database-migration". Move a PostgreSQL JSONB field to MySQL.

Expected outcome:

  • Map JSONB to MySQL JSON and identify queries that depend on PostgreSQL operators.
  • Validate document shape, indexing requirements, null behavior, and representative query results.
  • Define a staged cutover with source retention until reconciliation succeeds.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 28 static findings are false positives caused by Markdown code fences, JavaScript SQL template literals, and ordinary schema identifiers. The skill provides educational database migration examples and contains no command execution, system reconnaissance, prompt injection, or malicious intent.

1
Files scanned
445
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-database-migration/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-database-migration/security.svg)](https://skillstore.io/skills/sickn33-database-migration?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-database-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-database-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-database-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). database-migration security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-database-migration/audits/5

BibTeX citation

@techreport{sickn33-sickn33-database-migration-2026, author = {sickn33}, title = {database-migration security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-database-migration/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "database-migration security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-database-migration/audits/5" identifiers: - type: other value: "skillstore:sickn33-database-migration:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

4 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
wshobson Recommended

wshobson-database-migration

Skillstore Score 78
Evidence Confidence High
Skillstore usage 16
Updated

2026-08-21

sickn33 Current

sickn33-database-migration

Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

doyajin174-database-migration

Skillstore Score 70
Evidence Confidence High
Skillstore usage 4
Updated

2026-08-21

cleanexpo-database-migration

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 9
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Add a production schema field

Create an incremental schema change with a backfill, validation checks, and a tested rollback path.

Coordinate a zero-downtime release

Sequence compatible database and application changes while defining monitoring, cutover, and cleanup checkpoints.

Review migration readiness

Assess data integrity risks, rollback coverage, database differences, and verification criteria before approval.

Try These Prompts

Create a basic schema migration
Create a [Sequelize, TypeORM, or Prisma] migration that adds [field] to [table]. Include apply, rollback, validation, and test steps.
Plan a safe data backfill
Plan a migration from [source field] to [target fields] for [record count] records. Include batching, NULL handling, verification, and rollback.
Design a zero-downtime change
Design a zero-downtime migration to [rename or change] [column] on [table]. Separate database changes, application deployments, backfill, monitoring, and cleanup.
Prepare a cross-database migration
Prepare a PostgreSQL-to-MySQL migration for [scope]. Map incompatible types, preserve constraints, define cutover, test rollback, and state assumptions.

Best Practices

  • Test apply and rollback paths against production-like data before deployment.
  • Use small, backward-compatible changes with explicit verification checkpoints.
  • Back up critical data and monitor errors, locks, latency, and row counts.

Avoid

  • Do not combine unrelated destructive changes in one migration.
  • Do not remove old fields before all application versions stop using them.
  • Do not treat successful execution as proof of data correctness.

Frequently Asked Questions

Which migration tools does this skill cover?
It includes examples for Sequelize, TypeORM, and Prisma, plus general SQL and cross-database migration patterns.
Can it execute migrations?
No. It provides plans and examples that require review, adaptation, testing, and execution in your environment.
Does every migration include rollback guidance?
The skill emphasizes rollback operations, transactions, checkpoints, and backups. Some destructive changes still require separate data restoration plans.
Can it guarantee zero downtime?
No. Zero downtime depends on database behavior, traffic, locking, application compatibility, monitoring, and deployment coordination.
Does it support database engine changes?
Yes. It describes PostgreSQL and MySQL differences, but complete migrations need detailed type, query, index, and constraint analysis.
What information should I provide?
Provide the current schema, target schema, ORM and versions, database engine, data volume, traffic constraints, rollback window, and validation criteria.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

6 downloads ยท 157 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all