database-migrations-sql-migrations

name	database-migrations-sql-migrations
description	SQL Database Migration Strategy and Implementation workflow skill. Use this skill when the user needs SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off. Use when this capability is needed.
metadata	{"author":"diegosouzapw"}

SQL Database Migration Strategy and Implementation

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/database-migrations-sql-migrations from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.

SQL Database Migration Strategy and Implementation

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Context, Output Format, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when working on SQL database migration strategy and implementation tasks.
• Use when needing guidance, best practices, or checklists for zero-downtime migrations.
• Use when designing rollback procedures for critical schema changes.
• The task is unrelated to SQL database migration strategy.
• You need a different domain or tool outside this scope.
• Use when the request clearly matches the imported source intent: SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.

Operating Table

Situation	Start here	Why it matters
First-time use	metadata.json	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	ORIGIN.md	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	resources/implementation-playbook.md	Starts with the smallest copied file that materially changes execution
Supporting context	resources/implementation-playbook.md	Adds the next most relevant copied source file without loading the entire package
Handoff decision	## Related Skills	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Clarify goals, constraints, and required inputs.
2. Apply relevant best practices and validate outcomes.
3. Provide actionable steps and verification.
4. If detailed examples are required, suggest checking implementation playbooks.
5. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
6. Read the overview and provenance files before loading any copied upstream support files.
7. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.

Imported Workflow Notes

Imported: Instructions

• Clarify goals, constraints, and required inputs.
• Apply relevant best practices and validate outcomes.
• Provide actionable steps and verification.
• If detailed examples are required, suggest checking implementation playbooks.

Imported: Overview

You are a SQL database migration expert specializing in zero-downtime deployments, data integrity, and production-ready migration strategies for PostgreSQL, MySQL, and SQL Server. Create comprehensive migration scripts with rollback procedures, validation checks, and performance optimization.

Imported: Context

The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.

Examples

Example 1: Ask for the upstream workflow directly

Use @database-migrations-sql-migrations to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @database-migrations-sql-migrations against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @database-migrations-sql-migrations for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @database-migrations-sql-migrations using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/database-migrations-sql-migrations, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @conductor-validator - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @confluence-automation - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @content-creator - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @content-marketer - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
references	copied reference notes, guides, or background material from upstream	references/n/a
examples	worked examples or reusable prompts copied from upstream	examples/n/a
scripts	upstream helper scripts that change execution or validation	scripts/n/a
agents	routing or delegation notes that are genuinely part of the imported package	agents/n/a
assets	supporting assets or schemas copied from the source package	assets/n/a

• implementation-playbook.md

Imported Reference Notes

Imported: Resources

• Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.

Imported: Output Format

1. Migration Analysis Report: Detailed breakdown of changes
2. Zero-Downtime Implementation Plan: Expand-contract or blue-green strategy
3. Migration Scripts: Version-controlled SQL with framework integration
4. Validation Suite: Pre and post-migration checks
5. Rollback Procedures: Automated and manual rollback scripts
6. Performance Optimization: Batch processing, parallel execution
7. Monitoring Integration: Progress tracking and alerting

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

---

Source: diegosouzapw/awesome-omni-skills — distributed by TomeVault.