agentsclimarketplace

Data migration safety review

Skill motao123/dev-workflow-kit/data-migration-safety-review

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill data-migration-safety-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a schema change, backfill, data migration, or persistence-layer transition must be reviewed for rollout order, reversibility, backfill safety, and operational risk.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, as published. Nobody here has run it

Data Migration Safety Review

Use this skill when the main risk is changing persistent data safely rather than just changing code.

Trigger Conditions

Use this skill when:

  • a schema or database migration is planned
  • a backfill, reindex, or persistent data rewrite is involved
  • rollout order matters because old and new data shapes may coexist
  • reversibility, idempotency, or migration safety is unclear
  • the user wants a safety pass before running a high-risk data change

Do not use this skill for generic API compatibility questions or ordinary refactors with no persistence impact.

Workflow

  1. Identify the data surface under change.
  2. Clarify whether the change is additive, destructive, backfill-based, dual-write, or format-transitional.
  3. Identify rollout sequencing, coexistence windows, and rollback limits.
  4. Assess safety risks such as partial backfill, inconsistent reads, write drift, or irreversible mutation.
  5. Recommend the safest migration path and verification points.
  6. Call out what should be documented or operationally staged.

Output

For non-trivial work, provide:

  • migration type
  • main data safety risks
  • rollout and rollback constraints
  • verification or backfill checkpoints
  • recommended next step

Coordination

After migration review:

  • use api-contract-compatibility-review if data shape changes affect external contracts
  • use release-rollout-strategy if deployment order must be carefully staged
  • use docs-writer if runbooks or migration notes must be published

Invocation Examples

  • "Use data-migration-safety-review before we run this schema backfill in production."
  • "Use data-migration-safety-review to check whether this migration is safely reversible."
  • "Use data-migration-safety-review because old and new data shapes may coexist during rollout."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.