Skills database-migrations-sql-migrations
📦

database-migrations-sql-migrations

Content revision r2 High Risk ⚙️ External commands

Plan Safe Zero-Downtime SQL Migrations

Database migrations can lock tables, corrupt data, or leave applications incompatible. This skill creates staged plans with validation, rollback, batching, and zero-downtime strategies.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

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-migrations-sql-migrations" from https://skillstore.io/skills/sickn33-database-migrations-sql-migrations.md and its manifest at https://skillstore.io/api/skills/sickn33-database-migrations-sql-migrations/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

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.

Markdown detail GET /skills/sickn33-database-migrations-sql-migrations.md Signed manifest GET /api/skills/sickn33-database-migrations-sql-migrations/manifest Signed lockfile GET /api/skills/sickn33-database-migrations-sql-migrations/lockfile

Test it

Using "database-migrations-sql-migrations". Add a nullable verified_at column to a busy users table without stopping writes.

Expected outcome:

  • Expand: add the nullable column without changing existing reads or writes.
  • Migrate: backfill rows in monitored batches with replica-lag and lock thresholds.
  • Contract: enforce final constraints only after all application versions use the new column.
  • Rollback: stop the backfill and revert application behavior before removing schema changes.

Using "database-migrations-sql-migrations". Move order data into a new schema while keeping both application versions available.

Expected outcome:

  • Create the destination schema and verify constraints before enabling synchronization.
  • Dual-write new changes, backfill historical rows, and compare counts and checksums.
  • Switch reads gradually after validation, then retire synchronization during a later release.

Using "database-migrations-sql-migrations". Review a migration that adds a required column to a large production table.

Expected outcome:

The direct change may lock the table and reject existing rows. Add the column as nullable, backfill it, validate data, then enforce the constraint.

Security Audit

High Risk
v5 • 7/23/2026 Open versioned report

The skill contains documentation and code samples; none automatically execute commands or access SQLite files, so all 33 static alerts are false positives for those patterns. However, the rollback and Python examples interpolate unvalidated values into SQL and paths, creating adoption-time injection and file-selection risks. No prompt injection, network access, credential exfiltration, or hidden execution was found.

2
Files scanned
555
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (2)

High
resources/implementation-playbook.md:335-354
Rollback Script Uses Unvalidated Migration Input
The example inserts MIGRATION_VERSION directly into a SQL command and backup or migration paths. A crafted value could alter rollback SQL or select unintended files.
The parameter comes directly from the first positional argument and is interpolated into SQL and paths without an allowlist or SQL binding.
High
resources/implementation-playbook.md:249-256resources/implementation-playbook.md:372-386resources/implementation-playbook.md:410-432
Dynamic SQL Examples Interpolate Unchecked Identifiers
Validation and parallel migration examples build SQL with table or column names from input objects and method arguments. Untrusted values could change query structure.
The examples place input-derived identifiers into f-strings, and no identifier composition API or allowlist appears in the surrounding code.

Risk Factors

⚙️ External commands (3)
resources/implementation-playbook.md:339-340 resources/implementation-playbook.md:348 resources/implementation-playbook.md:330
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-migrations-sql-migrations/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-migrations-sql-migrations/security.svg)](https://skillstore.io/skills/sickn33-database-migrations-sql-migrations?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-database-migrations-sql-migrations.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-migrations-sql-migrations security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-database-migrations-sql-migrations/audits/5

BibTeX citation

@techreport{sickn33-sickn33-database-migrations-sql-migrations-2026, author = {sickn33}, title = {database-migrations-sql-migrations security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-database-migrations-sql-migrations/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-migrations-sql-migrations 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-migrations-sql-migrations/audits/5" identifiers: - type: other value: "skillstore:sickn33-database-migrations-sql-migrations:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Add Fields Without Downtime

Plan a backward-compatible schema change while old and new application versions run together.

Backfill Large Production Tables

Define batches, throttling, checkpoints, and validation for a high-volume data migration.

Build Migration Release Gates

Create deployment sequencing, rollback criteria, and verification steps for automated delivery workflows.

Try These Prompts

Plan a Basic Column Migration 
Create a safe migration plan to add [column] to [table] on [database]. Include prerequisites, validation checks, and rollback steps.
Design an Expand-Contract Change 
Design an expand-contract migration for [schema change] while [old version] and [new version] run concurrently. Include deployment order and compatibility checks.
Plan a Large-Table Backfill 
Plan a zero-downtime backfill for [table] containing [row count] rows. Define batch sizing, throttling, progress checks, failure recovery, and index handling.
Audit a Production Migration 
Review this proposed migration: [plan]. Identify locking, integrity, injection, rollback, and compatibility risks. Produce a revised sequence with go or no-go gates.

Best Practices

  • Collect engine version, table size, traffic patterns, replication limits, and recovery objectives before designing the migration.
  • Separate schema expansion, data backfill, application rollout, and schema contraction into independently verifiable releases.
  • Test forward and rollback paths with production-like data, then monitor locks, errors, lag, and migration progress.

Avoid

  • Do not run generated migration examples directly in production without environment-specific review and testing.
  • Do not combine destructive schema changes with application dependencies in one irreversible deployment.
  • Do not interpolate untrusted table names, column names, versions, or paths into SQL and shell commands.

Frequently Asked Questions

Which database engines does this skill cover?
It targets PostgreSQL, MySQL, and SQL Server, although detailed examples favor PostgreSQL.
Does the skill execute migrations?
No. It produces plans, scripts, checks, and rollback guidance for you to review and run.
Can it guarantee zero downtime?
No. Availability depends on engine behavior, schema size, workload, deployment order, and operational controls.
What information should I provide?
Provide the current schema, desired change, database version, row counts, traffic profile, deployment process, and recovery objectives.
Does it support migration frameworks?
Yes. The playbook includes Flyway and Alembic patterns that require adaptation to your project.
How should destructive changes be handled?
Use backups, staged compatibility releases, explicit validation gates, tested rollback procedures, and qualified human approval.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/database-migrations-sql-migrations

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

9 downloads · 110 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all